Re: Some tickets that need love before 1.3 feature freeze.

On Wed, Dec 15, 2010 at 3:29 PM, Shai Berger wrote: > Hi, > > On Tuesday 14 December 2010, Russell Keith-Magee wrote: >> >> From an initial inspection, none of these tickets are subject to the >> feature freeze, because none of them are features. They're all bugs >> (which are

Re: Some tickets that need love before 1.3 feature freeze.

Hi, On Tuesday 14 December 2010, Russell Keith-Magee wrote: > > From an initial inspection, none of these tickets are subject to the > feature freeze, because none of them are features. They're all bugs > (which are fair game until the RC) or documentation updates (which are > fair game right up

Re: problem to run server

python manage.py syncdb also shows this error only.import django in python shell works; i am using postgres every thing is fine it seems in postgres. -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to

Re: Python 3

On Wed, Dec 15, 2010 at 6:52 AM, mofle wrote: > Is there any plan or roadmap for porting Django to Python 3? > > The latest info I could is from 1 year ago. Nothing has really changed since a year ago. Python 3 support is on our long term roadmap, but we're not planning to

Python 3

Is there any plan or roadmap for porting Django to Python 3? The latest info I could is from 1 year ago. -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-develop...@googlegroups.com. To

Re: Security - contrib.auth hashing

On Tuesday, July 20, 2010 2:23:52 PM UTC-4, Craig Younkins wrote: > > Maybe. The issue in my mind with bcrypt and scrypt is that they are not > validated by NIST or NSA, unlike SHA-2. Blowfish was examined by NIST for > the AES competition but to my knowledge the use of hashing has not been. >

Re: problem to run server

Hi, This list for developing Django itself, not developing with Django. Please move this discussion to django-users. Thanks. --- Łukasz Rekucki On 14 December 2010 13:55, Tonton wrote: > i presume that in your file you have write > > from django*... import  . 

Re: more than one querys LIKE in the same field

django-developers is for the discussion of the development of Django itself, not development with Django. As such this mailing list is not appropriate for this message, django-users would be more appropriate. -- Gert Mobile: +32 498725202 Twitter: @gvangool Web:

Re: problem to run server

i presume that in your file you have write from django*... import . is there the trouble .. may be in your settings with database does your manage.py syncdb has work ? On Tue, Dec 14, 2010 at 8:16 AM, NavaTux wrote: > I want to test django application so when i

Re: Enabling context access in simple_tag

On Dec 14, 12:02 am, Julien Phalip wrote: > On Dec 13, 10:16 am, Tai Lee wrote: > > -snip- > > > One suggestion from #1105 was to split out this functionality into > > individual decorators, @takes_context, @takes_block. I'm not sure how > > easy this

more than one querys LIKE in the same field

Hi friends! I mean do something like this: SELECT * FROM table WHERE tags LIKE '%candy%' AND tags LIKE '%milk%' I've tried: table.objects.filter(tags__icontains='candy', tags__icontains='milk') I've tried too: list = ['candy', 'milk'] table.objects.filter(tags__icontains=list And nothing

problem to run server

I want to test django application so when i created the project "django-admin.py start project testp" and i created application python manage.py startapp testapp then i added in settings.py (database postgresql_psycopg2,name,username,password) as well as i am running in virtualenv,installed fine

Re: Enabling context access in simple_tag

On Dec 13, 10:16 am, Tai Lee wrote: -snip- > One suggestion from #1105 was to split out this functionality into > individual decorators, @takes_context, @takes_block. I'm not sure how > easy this would be technically to implement, but I think it would > solve the