FWIW, I have several small, public-facing Django projects, all of which are
on Django 1.5.1/Python 3.3. I've had no trouble with them at all.
I've wanted to switch to Python 3 for a while, but it's only been in the
past year (thanks in large part to Django's move) that it's become
practical.
On Thu, Apr 11, 2013 at 9:36 PM, Mark Lybrand 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
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 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 r
>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"
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
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 l
6 matches
Mail list logo
