On Dec 15, 10:52 pm, Russell Keith-Magee
wrote:
> On Wed, Dec 15, 2010 at 6:41 PM, Julien Phalip wrote:
> > On Dec 14, 7:34 pm, Christian Hammond wrote:
> >> On Dec 14, 12:02 am, Julien Phalip wrote:
>
> >> > On Dec 13, 10:16 am, Tai Lee wrote:
>
> >> > -snip-
>
> >> > > One suggestion from #1
On Thursday, December 16, 2010 4:11:25 AM UTC+11, Łukasz Rekucki wrote:
>
> But there has been some significant progress in that matter, like the new
> email package or PEP 444 (http://www.python.org/dev/peps/pep-0444/).
PEP and not PEP 444 is likely the more probable target for deployin
Any chance this one (#16455) can be reviewed before feature freeze?
Thanks. Kent
On Dec 3, 1:16 am, KentH wrote:
> Ian's comments were spot-on. And it's extremely helpful when a
> critique comes complete with a better solution.
>
> I've uploaded the improved code patch. Docs & tests unchanged.
>
http://docs.djangoproject.com/en/dev/faq/install/#can-i-use-django-with-python-3
On Dec 15, 5:45 am, sirex wrote:
> On 15 Gruo, 01:51, Russell Keith-Magee
> wrote:
>
> > but we're not planning to actively support Python 3 any time soon.
>
> Why?
>
> Maybe there should be two versions of Django,
I have produced a patch for this [1] long-standing SQL bug.
The SQL produced with the patch is correct AFAIK, but my understanding
of the sql code is rather poor so I'm hoping that someone who knows
better will give it a look. There might be a more correct/elegant way
to fix this.
[1] http://code
On 15 December 2010 17:48, Ian Kelly wrote:
> On Wed, Dec 15, 2010 at 12:45 AM, sirex wrote:
>> On 15 Gruo, 01:51, Russell Keith-Magee
>> wrote:
>>> but we're not planning to actively support Python 3 any time soon.
>>
>> Why?
>
> Dependencies, for one.
Apart from external ones, there are still
On Wed, Dec 15, 2010 at 12:45 AM, sirex wrote:
> On 15 Gruo, 01:51, Russell Keith-Magee
> wrote:
>> but we're not planning to actively support Python 3 any time soon.
>
> Why?
Dependencies, for one. Psycopg2 and MySQLdb do not officially support
Python 3 yet, so the only backends available out
On Wed, Dec 15, 2010 at 3:45 PM, sirex wrote:
> On 15 Gruo, 01:51, Russell Keith-Magee
> wrote:
>> but we're not planning to actively support Python 3 any time soon.
>
> Why?
Please search the archives, and the FAQ, for the answer to this
question. It's been answered *many* times.
Yours,
Russ M
On 15 Gruo, 01:51, Russell Keith-Magee
wrote:
> but we're not planning to actively support Python 3 any time soon.
Why?
Maybe there should be two versions of Django, one that supports Python
3 and other that supports Python 2?
--
You received this message because you are subscribed to the Goog
On Wed, Dec 15, 2010 at 6:41 PM, Julien Phalip wrote:
> On Dec 14, 7:34 pm, Christian Hammond wrote:
>> 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
>> > > ind
On Dec 14, 7:34 pm, Christian Hammond wrote:
> 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
11 matches
Mail list logo