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

[Russell Keith-Magee]

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 fair game until the RC) or documentation updates (which are
>> fair game right up until the final release).
>>
> What about http://code.djangoproject.com/ticket/9964 ?
>
> It's a bug, but the suggested fix includes behavior change and possibly even a
> backward-incompatible change.
>
> Does the feature freeze apply?

The feature freeze only ever applies to *features*.

In the case of #9964, there is no new feature, it's a correction to
existing behavior. As I noted last time you raised this ticket, the
only question is whether this is genuinely a bug, or a behavioral
misfeature that needs correcting. If it's a bug, then no backwards
compatibility issue exists, because bugs aren't covered by our
backwards compatibility policy.

FYI - I had a quick look at #9964 during the recent Sydney sprint, but
not enough to push the ticket forward or commit it; I was intending to
give #9964 a solid look once the feature freeze happens.

Yours,
Russ Magee %-)

-- 
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 unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

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

[Shai Berger]

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 until the final release).
> 
What about http://code.djangoproject.com/ticket/9964 ?

It's a bug, but the suggested fix includes behavior change and possibly even a 
backward-incompatible change.

Does the feature freeze apply?

Thanks,
Shai.

-- 
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 unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Re: problem to run server

[NavaTux]

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 django-develop...@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Re: Python 3

[Russell Keith-Magee]

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 actively support
Python 3 any time soon.

Yours,
Russ Magee %-)

-- 
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 unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Python 3

[mofle]

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 unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Re: Security - contrib.auth hashing

[Bret W]

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. 
> SHA-2 was developed by NSA and is recommended by NIST (
> http://csrc.nist.gov/groups/ST/toolkit/secure_hashing.html).
>
> That being said, I'm asking the opinion of a few other folks at OWASP and 
> trying to get a consensus of 1 sentence to summarize how passwords should be 
> stored. In my mind, this sentence should be "Use a SHA-2 algorithm with a 
> 64-bit random salt and 1000 iterations," but this statement is my own and 
> does not necessarily reflect the views of OWASP. I'll post here 
> with developments.
>

I wanted to follow up on this discussion to see if any further thought had 
been given to using bcrypt.

With the recent Gawker hacking incident, there has been another round of 
discussion happening regarding best practices for securely storing 
credentials, and from the discussions I've seen at Hacker News, those in the 
know are still recommending bcrypt.

I am not a security researcher or a cryptographer, so I don't have much to 
add to this conversation, other than that I want to be sure that Django's 
following the best practices put forth by security professionals.

Backward compatibility is definitely an issue to be addressed, and it's not 
in the scope of this message to do so, but I would like to say that some 
changes worth ugly fixes. It's obvious that it's not possible to rehash 
passwords that application developers don't have, so it seems likely that 
there's going to need to be a hack to support an old and a new hashing 
scheme for a couple of versions of Django. I believe most developers would 
be accepting of a little interim cruft if it meant a more secure product in 
the long term.

While we're on the subject of security, have the security-related pieces of 
Django ever undergone a security audit? I remember Simon W. asking for a 
code review of his signed-cookie implementation 
(https://groups.google.com/forum/#topic/django-developers/KX6LIgBvfzo), and 
I now see that Jacob didn't feel that a security audit was worthwhile, given 
what the DSF can afford and the implications for peer review. If 
contrib.auth hasn't been reviewed by a security expert, I'd like to suggest 
that someone investigate the possibility of having it reviewed. Security, 
and specifically cryptography, is one area of computing that requires tons 
of expertise. Even with many eyeballs, it's hard to be certain that a 
salient detail wasn't overlooked. That being said, I'm not close to the 
framework development process, and I don't know what's been done in the past 
or who's been consulted.

Bret

-- 
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 unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Re: problem to run server

[Łukasz Rekucki]

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  .  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 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 of(psycopg2,django 1.1)
>>
>> when i ran a server i got the error
>>
>> " (test)hire...@hirelex-laptop:~/test/testp$ python manage.py
>> runserver
>> Validating models...
>> Unhandled exception in thread started by > 0x9f266bc>
>> Traceback (most recent call last):
>>  File "/usr/local/lib/python2.6/dist-packages/django/core/management/
>> commands/runserver.py", line 48, in inner_run
>>    self.validate(display_num_errors=True)
>>  File "/usr/local/lib/python2.6/dist-packages/django/core/management/
>> base.py", line 249, in validate
>>    num_errors = get_validation_errors(s, app)
>>  File "/usr/local/lib/python2.6/dist-packages/django/core/management/
>> validation.py", line 22, in get_validation_errors
>>    from django.db import models, connection
>>  File "/usr/local/lib/python2.6/dist-packages/django/db/__init__.py",
>> line 77, in 
>>    connection = connections[DEFAULT_DB_ALIAS]
>>  File "/usr/local/lib/python2.6/dist-packages/django/db/utils.py",
>> line 91, in __getitem__
>>    backend = load_backend(db['ENGINE'])
>>  File "/usr/local/lib/python2.6/dist-packages/django/db/utils.py",
>> line 22, in load_backend
>>    module = import_module('.base', 'django.db.backends.%s' %
>> backend_name)
>>  File "/usr/local/lib/python2.6/dist-packages/django/utils/
>> importlib.py", line 35, in import_module
>>    __import__(name)
>> ValueError: Empty module name
>>
>> "
>>
>> May i know the problem ?please suggest me
>>
>> pip freeze
>>
>> " Brlapi==0.5.4
>> CouchDB==0.6
>> Django==1.2.3
>> GnuPGInterface==0.3.2
>> Mako==0.2.5
>> PAM==0.4.2
>> PIL==1.1.7
>> PyOpenGL==3.0.0
>> Pygments==1.2.2
>> Twisted-Core==10.0.0
>> Twisted-Names==10.0.0
>> Twisted-Web==10.0.0
>> adium-theme-ubuntu==0.1
>> apturl==0.4.1ubuntu4
>> command-not-found==0.1
>> configglue==0.2dev
>> cups==1.0
>> distribute==0.6.10
>> django-tagging==0.3.1
>> docutils==0.6
>> egenix-mx-base==3.1.3
>> fstab==1.4
>> gdata.py==1.2.4
>> gnome-app-install==0.4.2ubuntu2
>> hgview==1.1.3
>> httplib2==0.6.0
>> human-theme==0.39
>> jockey==0.5.8
>> launchpadlib==1.6.0
>> lazr.restfulclient==0.9.11
>> lazr.uri==1.0.2
>> louis==1.7.0
>> lxml==2.2.4
>> mercurial==1.4.3
>> nvidia-common==0.0.0
>> oauth==1.0a
>> onboard==0.93.0
>> papyon==0.4.8
>> pexpect==2.3
>> protobuf==2.2.0
>> psycopg2==2.3.1
>> pyOpenSSL==0.10
>> pycrypto==2.0.1
>> pycurl==7.19.0
>> pyinotify==0.8.9
>> pyserial==2.3
>> python-apt==0.7.94.2ubuntu6.2
>> python-debian==0.1.14ubuntu2
>> python-launchpad-bugs==0.3.6
>> pyusb==0.4.2
>> pyxdg==0.18
>> rdflib==2.4.2
>> screen-resolution-extra==0.0.0
>> simplejson==2.0.9
>> smbc==1.0
>> speechd==0.3
>> speechd-config==0.0
>> system-service==0.1.6
>> ubuntu-gdm-themes==0.33
>> ubuntuone-storage-protocol==1.2.0
>> ufw==0.30pre1-0ubuntu2
>> unattended-upgrades==0.1
>> usb-creator==0.2.22
>> vboxapi==1.0
>> virtkey==0.01
>> virtualenv==1.4.5
>> wadllib==1.1.4
>> wsgiref==0.1.2
>> xkit==0.0.0
>> zope.interface==3.5.3
>> (test)hire...@hirelex-laptop:~/test/testp$
>>  "
>>
>> --
>> 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 unsubscribe from this group, send email to
>> django-developers+unsubscr...@googlegroups.com.
>> For more options, visit this group at
>> http://groups.google.com/group/django-developers?hl=en.
>>
>
> --
> 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 unsubscribe from this group, send email to
> django-developers+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/django-developers?hl=en.
>

-- 
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 unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Re: more than one querys LIKE in the same field

[Gert Van Gool]

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: http://gert.selentic.net



On Tue, Dec 14, 2010 at 09:14, marcoarreguin wrote:

> 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 work. Help me please :s
>
> Thanks bros!
>
> --
> 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 unsubscribe from this group, send email to
> django-developers+unsubscr...@googlegroups.com
> .
> For more options, visit this group at
> http://groups.google.com/group/django-developers?hl=en.
>
>

-- 
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 unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Re: problem to run server

[Tonton]

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 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 of(psycopg2,django 1.1)
>
> when i ran a server i got the error
>
> " (test)hire...@hirelex-laptop:~/test/testp$ python manage.py
> runserver
> Validating models...
> Unhandled exception in thread started by  0x9f266bc>
> Traceback (most recent call last):
>  File "/usr/local/lib/python2.6/dist-packages/django/core/management/
> commands/runserver.py", line 48, in inner_run
>self.validate(display_num_errors=True)
>  File "/usr/local/lib/python2.6/dist-packages/django/core/management/
> base.py", line 249, in validate
>num_errors = get_validation_errors(s, app)
>  File "/usr/local/lib/python2.6/dist-packages/django/core/management/
> validation.py", line 22, in get_validation_errors
>from django.db import models, connection
>  File "/usr/local/lib/python2.6/dist-packages/django/db/__init__.py",
> line 77, in 
>connection = connections[DEFAULT_DB_ALIAS]
>  File "/usr/local/lib/python2.6/dist-packages/django/db/utils.py",
> line 91, in __getitem__
>backend = load_backend(db['ENGINE'])
>  File "/usr/local/lib/python2.6/dist-packages/django/db/utils.py",
> line 22, in load_backend
>module = import_module('.base', 'django.db.backends.%s' %
> backend_name)
>  File "/usr/local/lib/python2.6/dist-packages/django/utils/
> importlib.py", line 35, in import_module
>__import__(name)
> ValueError: Empty module name
>
> "
>
> May i know the problem ?please suggest me
>
> pip freeze
>
> " Brlapi==0.5.4
> CouchDB==0.6
> Django==1.2.3
> GnuPGInterface==0.3.2
> Mako==0.2.5
> PAM==0.4.2
> PIL==1.1.7
> PyOpenGL==3.0.0
> Pygments==1.2.2
> Twisted-Core==10.0.0
> Twisted-Names==10.0.0
> Twisted-Web==10.0.0
> adium-theme-ubuntu==0.1
> apturl==0.4.1ubuntu4
> command-not-found==0.1
> configglue==0.2dev
> cups==1.0
> distribute==0.6.10
> django-tagging==0.3.1
> docutils==0.6
> egenix-mx-base==3.1.3
> fstab==1.4
> gdata.py==1.2.4
> gnome-app-install==0.4.2ubuntu2
> hgview==1.1.3
> httplib2==0.6.0
> human-theme==0.39
> jockey==0.5.8
> launchpadlib==1.6.0
> lazr.restfulclient==0.9.11
> lazr.uri==1.0.2
> louis==1.7.0
> lxml==2.2.4
> mercurial==1.4.3
> nvidia-common==0.0.0
> oauth==1.0a
> onboard==0.93.0
> papyon==0.4.8
> pexpect==2.3
> protobuf==2.2.0
> psycopg2==2.3.1
> pyOpenSSL==0.10
> pycrypto==2.0.1
> pycurl==7.19.0
> pyinotify==0.8.9
> pyserial==2.3
> python-apt==0.7.94.2ubuntu6.2
> python-debian==0.1.14ubuntu2
> python-launchpad-bugs==0.3.6
> pyusb==0.4.2
> pyxdg==0.18
> rdflib==2.4.2
> screen-resolution-extra==0.0.0
> simplejson==2.0.9
> smbc==1.0
> speechd==0.3
> speechd-config==0.0
> system-service==0.1.6
> ubuntu-gdm-themes==0.33
> ubuntuone-storage-protocol==1.2.0
> ufw==0.30pre1-0ubuntu2
> unattended-upgrades==0.1
> usb-creator==0.2.22
> vboxapi==1.0
> virtkey==0.01
> virtualenv==1.4.5
> wadllib==1.1.4
> wsgiref==0.1.2
> xkit==0.0.0
> zope.interface==3.5.3
> (test)hire...@hirelex-laptop:~/test/testp$
>  "
>
> --
> 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 unsubscribe from this group, send email to
> django-developers+unsubscr...@googlegroups.com
> .
> For more options, visit this group at
> http://groups.google.com/group/django-developers?hl=en.
>
>

-- 
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 unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Re: Enabling context access in simple_tag

[Christian Hammond]

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 would be technically to implement, but I think it would
> > solve the `takes_context_plus` sink problem Malcolm describes as we
> > potentially add more special case tag types (simple, inclusion,
> > assignment, etc.)
>
> The djblets (created by the guys at reviewboard.org) contain two nifty
> decorators for exactly this purpose:
> @basictag:https://github.com/djblets/djblets/blob/master/djblets/util/decorator...
> @blocktag:https://github.com/djblets/djblets/blob/master/djblets/util/decorator...
>
> This now seems to me like the perfect compromise. It would generally
> allow for more versatility and to keep simple_tag (and the future
> assignment_tag) free of takes_xxx cruft.
>
> Any chance these two decorators could be considered for inclusion in
> Django core?

For what it's worth, these two decorators have seriously cut down on
our development and maintenance burdens. Whether they'd be sufficient
as-is, I don't know (though you're welcome to have the code), but I'd
also love to see equivalent functionality in Django.

If I can help in some way to get these in shape (assuming you'd want
to go that direction), just let me know.

Christian

-- 
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 unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

more than one querys LIKE in the same field

[marcoarreguin]

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 work. Help me please :s

Thanks bros!

-- 
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 unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

problem to run server

[NavaTux]

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 of(psycopg2,django 1.1)

when i ran a server i got the error

" (test)hire...@hirelex-laptop:~/test/testp$ python manage.py
runserver
Validating models...
Unhandled exception in thread started by 
Traceback (most recent call last):
  File "/usr/local/lib/python2.6/dist-packages/django/core/management/
commands/runserver.py", line 48, in inner_run
self.validate(display_num_errors=True)
  File "/usr/local/lib/python2.6/dist-packages/django/core/management/
base.py", line 249, in validate
num_errors = get_validation_errors(s, app)
  File "/usr/local/lib/python2.6/dist-packages/django/core/management/
validation.py", line 22, in get_validation_errors
from django.db import models, connection
  File "/usr/local/lib/python2.6/dist-packages/django/db/__init__.py",
line 77, in 
connection = connections[DEFAULT_DB_ALIAS]
  File "/usr/local/lib/python2.6/dist-packages/django/db/utils.py",
line 91, in __getitem__
backend = load_backend(db['ENGINE'])
  File "/usr/local/lib/python2.6/dist-packages/django/db/utils.py",
line 22, in load_backend
module = import_module('.base', 'django.db.backends.%s' %
backend_name)
  File "/usr/local/lib/python2.6/dist-packages/django/utils/
importlib.py", line 35, in import_module
__import__(name)
ValueError: Empty module name

"

May i know the problem ?please suggest me

pip freeze

" Brlapi==0.5.4
CouchDB==0.6
Django==1.2.3
GnuPGInterface==0.3.2
Mako==0.2.5
PAM==0.4.2
PIL==1.1.7
PyOpenGL==3.0.0
Pygments==1.2.2
Twisted-Core==10.0.0
Twisted-Names==10.0.0
Twisted-Web==10.0.0
adium-theme-ubuntu==0.1
apturl==0.4.1ubuntu4
command-not-found==0.1
configglue==0.2dev
cups==1.0
distribute==0.6.10
django-tagging==0.3.1
docutils==0.6
egenix-mx-base==3.1.3
fstab==1.4
gdata.py==1.2.4
gnome-app-install==0.4.2ubuntu2
hgview==1.1.3
httplib2==0.6.0
human-theme==0.39
jockey==0.5.8
launchpadlib==1.6.0
lazr.restfulclient==0.9.11
lazr.uri==1.0.2
louis==1.7.0
lxml==2.2.4
mercurial==1.4.3
nvidia-common==0.0.0
oauth==1.0a
onboard==0.93.0
papyon==0.4.8
pexpect==2.3
protobuf==2.2.0
psycopg2==2.3.1
pyOpenSSL==0.10
pycrypto==2.0.1
pycurl==7.19.0
pyinotify==0.8.9
pyserial==2.3
python-apt==0.7.94.2ubuntu6.2
python-debian==0.1.14ubuntu2
python-launchpad-bugs==0.3.6
pyusb==0.4.2
pyxdg==0.18
rdflib==2.4.2
screen-resolution-extra==0.0.0
simplejson==2.0.9
smbc==1.0
speechd==0.3
speechd-config==0.0
system-service==0.1.6
ubuntu-gdm-themes==0.33
ubuntuone-storage-protocol==1.2.0
ufw==0.30pre1-0ubuntu2
unattended-upgrades==0.1
usb-creator==0.2.22
vboxapi==1.0
virtkey==0.01
virtualenv==1.4.5
wadllib==1.1.4
wsgiref==0.1.2
xkit==0.0.0
zope.interface==3.5.3
(test)hire...@hirelex-laptop:~/test/testp$
 "

-- 
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 unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Re: Enabling context access in simple_tag

[Julien Phalip]

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 `takes_context_plus` sink problem Malcolm describes as we
> potentially add more special case tag types (simple, inclusion,
> assignment, etc.)

The djblets (created by the guys at reviewboard.org) contain two nifty
decorators for exactly this purpose:
@basictag: 
https://github.com/djblets/djblets/blob/master/djblets/util/decorators.py#L96
@blocktag: 
https://github.com/djblets/djblets/blob/master/djblets/util/decorators.py#L161

This now seems to me like the perfect compromise. It would generally
allow for more versatility and to keep simple_tag (and the future
assignment_tag) free of takes_xxx cruft.

Any chance these two decorators could be considered for inclusion in
Django core?

Cheers,

Julien

-- 
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 unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.