I believe pillow supports python 3, you can use it as a drop in replacement
of PIL


On Thu, Apr 11, 2013 at 6:21 PM, Timothy Makobu <[email protected]
> wrote:

> From the release notes 
> https://docs.djangoproject.com/en/dev/releases/1.5/"Django
> 1.6, will support Python 3 without reservations."
>
> And from the release-process
> https://docs.djangoproject.com/en/1.2/internals/release-process/ "Minor
> release (1.1, 1.2, etc.) will happen roughly every nine months"
>
> So towards the end of the year we'll have 1.6.
>
>
> On Thu, Apr 11, 2013 at 4:48 PM, Thomas Weholt <[email protected]>wrote:
>
>> I develop my current project with python 2.7 and 3.3 and so far my
>> problem is not with django being 3.x compatible but critical/popular
>> third-party packages like PIL, django-debug-toolbar etc not being python 3
>> ready. I hope those and several other packages will be ported to python 3,
>> since Python 3 has some very nice features not available in 2.x and it
>> solves all my unicode issues being a programmer which often deal with
>> non-english characters.
>>
>> So far I've had no problems using python 3 and django. All problems I've
>> encountered has been caused by thrid-party packages, my own packages
>> included :-|
>>
>>
>> On Thu, Apr 11, 2013 at 3:36 PM, Mark Lybrand <[email protected]> wrote:
>>
>>> I understand that there is only experimental support for Python 3.x in
>>> Django 1.5.  Is there any feeling for how far out a stable version of
>>> Django using Python 3.x might be?  I understand that any answer is likely
>>> to be conjecture and guessing and that is okay.  I am just trying to gauge
>>> if I am looking at a matter of months or a year or if it something that may
>>> be 3 or 5 or more years out.
>>>
>>> Thanks in advance.
>>>
>>> --
>>> Mark :)
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "Django users" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to [email protected].
>>> To post to this group, send email to [email protected].
>>> Visit this group at http://groups.google.com/group/django-users?hl=en.
>>> For more options, visit https://groups.google.com/groups/opt_out.
>>>
>>>
>>>
>>
>>
>>
>> --
>> Mvh/Best regards,
>> Thomas Weholt
>> http://www.weholt.org
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Django users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to [email protected].
>> To post to this group, send email to [email protected].
>> Visit this group at http://groups.google.com/group/django-users?hl=en.
>> For more options, visit https://groups.google.com/groups/opt_out.
>>
>>
>>
>
>  --
> You received this message because you are subscribed to the Google Groups
> "Django users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> To post to this group, send email to [email protected].
> Visit this group at http://groups.google.com/group/django-users?hl=en.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/django-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to