On Sat, Mar 6, 2010 at 11:53 AM, Brian Neal wrote:
> Thanks Karen. Yes, I'm using Ubuntu, and running with --noreload
> allows me to see the PendingDeprecationWarning. Is this worthy of a
> bug report?
>
Sure. Just please don't put it in the 1.2 milestone; it's not a release
blocker.
Karen
--
On Mar 6, 10:29 am, Karen Tracey wrote:
> This appears to be due to the way runserver reloads the process when
> monitoring for source code changes. If you specify --noreload on runserver
> I bet you will see the warnings. The behavior appears to be OS-specific: I
> can recreate what you describe
On Fri, Mar 5, 2010 at 9:28 PM, Brian Neal wrote:
> Any ideas? Can anyone else try this and report back? Just insert the
> code below into a view function and start the dev. server with "python
> -Wall manage.py runserver". Thanks.
>
This appears to be due to the way runserver reloads the proces
On Mar 6, 2:28 am, Brian Neal wrote:
> Any ideas? Can anyone else try this and report back? Just insert the
> code below into a view function and start the dev. server with "python
> -Wall manage.py runserver". Thanks.
Hi,
Just to confirm I tried it and can't see them either, on python 2.6.
Don'
Any ideas? Can anyone else try this and report back? Just insert the
code below into a view function and start the dev. server with "python
-Wall manage.py runserver". Thanks.
On Feb 28, 5:28 pm, Brian Neal wrote:
> I'm having trouble seeing PendingDeprecationWarning's on stderr when
> using the
I'm having trouble seeing PendingDeprecationWarning's on stderr when
using the dev server.
To make sure I'm not crazy, I wrote a simple Python program that looks
like this:
print "** WARNING **"
import warnings
warnings.warn(
"Testing the warnings module!",
6 matches
Mail list logo