On Fri, Aug 10, 2012 at 3:45 PM, Simon Meers wrote:
> > On 10 August 2012 18:56, Vinay Sajip wrote:
> >> I think Option 2 is better, for the reasons you state.
>
> +1. And it's not too entangled to be easily stripped out if/when
> Python 2 support is removed.
>
> On 11 August 2012 06:10, Łukasz
> On 10 August 2012 18:56, Vinay Sajip wrote:
>> I think Option 2 is better, for the reasons you state.
+1. And it's not too entangled to be easily stripped out if/when
Python 2 support is removed.
On 11 August 2012 06:10, Łukasz Rekucki wrote:
> How about wrapping those 3 lines of code into a
On 10 August 2012 18:56, Vinay Sajip wrote:
> I think Option 2 is better, for the reasons you state.
>
How about wrapping those 3 lines of code into a class decorator
(preferably named more explicit then StrAndUnicode) ? That would be at
least a little DRY.
--
Łukasz Rekucki
--
You received t
That sounds good to me, though I'm not a committer on the tree as far
as I know. Anssi?
On Fri, Aug 10, 2012 at 8:12 AM, Flavio Curella
wrote:
> Just to clarify, the plan is:
>
> 1) Merge in patch v8 (2d index for 2-dimensional fields, _nd index for 3D
> and up)
> 2) Open a new ticket for the
I think Option 2 is better, for the reasons you state.
Regards,
Vinay Sajip
--
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 emai
Just to clarify, the plan is:
1) Merge in patch v8 (2d index for 2-dimensional fields, _nd index for 3D
and up)
2) Open a new ticket for the new 3D operators.
Let me know if that sounds good, or if you can think of any way of
improving the patch.
Thanks,
Flavio.
On Thursday, August 9, 2012 5:
This question was answered on the django-users list where it was also
posted. Please do not cross-post to both lists. The right list for usage
questions like this is django-users.
Karen
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To po
Le vendredi 10 août 2012 05:28:42 UTC+2, Daniel Sokolowski a écrit :
>
> I prefer Proposal 2 out of the list, and regarding Russell's point I
> believe that the tutorial ought to promote Python 3 and be written from
> that perspective with Python 2 exceptions - because exactly of Django's
> imp
As you know, Django can process file uploading with its own
uploadhandler. But all the request data is processed as stream, and
mod_wsgi provides a way to read the stream, what you can do is just
read the stream sequentially, which means that you cannot separate
file stream from the request input
