On Tue, Dec 27, 2011 at 12:12 PM, Justin Holmes wrote:
> Yep, there's no doubt that having these kinds of discussions on the
> dev list (which already struggles at times to keep a good signal /
> noise ratio) is not the way.
>
> However, it was clear at djangocon (and is also clear in the various
>
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com.
To unsubscribe from this group, send email to
django-developers+unsubscr...@googlegroups.com.
For more options, vi
Yep, there's no doubt that having these kinds of discussions on the
dev list (which already struggles at times to keep a good signal /
noise ratio) is not the way.
However, it was clear at djangocon (and is also clear in the various
django IRC channels) that:
1) Many django developers are politic
While this bill certainly merits discussion, and may indeed be related
to sites created with and using Django, this forum is not the place
for it. Please do not continue this thread here.
-Paul
--
You received this message because you are subscribed to the Google Groups
"Django developers" grou
On 12/26/2011 07:46 PM, Jeremy Dunck wrote:
On Mon, Dec 26, 2011 at 4:33 PM, Etienne Robillard wrote:
What thus you Django developers all think of this proposed law and how could
this may affect open source communities such as Django and Python
to develop novel apps specifically for creating us
On Mon, Dec 26, 2011 at 4:33 PM, Etienne Robillard wrote:
> What thus you Django developers all think of this proposed law and how could
> this may affect open source communities such as Django and Python
> to develop novel apps specifically for creating user-generated content?
This feels off-top
Hi,
I'm curious and at the same time a little worried by the upcoming "SOPA"
bill, which would imposes in US new laws for blocking down websites and
user-generated content on the basis of copyright violation.
What thus you Django developers all think of this proposed law and how
could this m
As it seems likely that Python 2.5 compatibility will be dropped for
Django 1.5, I've updated the Python 3 port[1] to remove the hacks
needed for 2.5 compatibility. This means:
1. The u() and b() calls have been removed, and replaced with removing
the u prefixes and adding "from __future__ import
Hello everyone,
I asked around in #django-dev but nobody had much to say, so I decided to
come here instead.
Currently, developers writing class-based views[0] use SelectObjectMixin[1]
to define which object will be handled by a given single-object view
instance (e.g. DetailView).
If I am unders
I suppose I should read the whole doc and not just ctrl-F before reporting
omissions. :)
On Dec 25, 2011, at 10:03 PM, Karen Tracey wrote:
> On Mon, Dec 26, 2011 at 12:58 AM, Jeremy Dunck wrote:
> I think Multi-TZ should get soms love in the release notes.
>
> https://code.djangoproject.co
10 matches
Mail list logo
