I'm sure Python 3 is wonderful, but I make heavy use of the Python
Imaging Library, which as I understand it has not been adapted to
Python 3. There may be alternatives, but as I have a large amount of
working code using PIL I am reluctant to drop it just yet.
Peter
--
http://mail.python.org/mai
You get some of the good stuff by importing future, unicode literals
which essentially means you're working in unicode by default most of the
time, and print function, (a small fix but long overdue).
I try to write python3 whenever I can. It's rare that dependencies keep
me back. More often
On 01/05/2012 03:41 PM, Evan Driscoll wrote:
On 1/4/2012 9:56 AM, Sean Wolfe wrote:
I am still living in the 2.x world because all the things I want to do
right now in python are in 2 (django, pygame). But I want to be
excited about the future of the language. I understand the concept of
needing
On 1/4/2012 9:56 AM, Sean Wolfe wrote:
> I am still living in the 2.x world because all the things I want to do
> right now in python are in 2 (django, pygame). But I want to be
> excited about the future of the language. I understand the concept of
> needing to break backwards compatibility. But i
On Jan 4, 9:56 am, Sean Wolfe wrote:
> I am still living in the 2.x world because all the things I want to do
> right now in python are in 2 (django, pygame). But I want to be
> excited about the future of the language.
Okay. So why not enjoy the best of both worlds (almost) and use
version 2.7.2
On 1/4/2012 9:56 AM, Sean Wolfe wrote:
> I am still living in the 2.x world because all the things I want to do
> right now in python are in 2 (django, pygame). But I want to be
> excited about the future of the language. I understand the concept of
> needing to break backwards compatibility. But i
On Wed, Jan 4, 2012 at 8:56 AM, Sean Wolfe wrote:
> I am still living in the 2.x world because all the things I want to do
> right now in python are in 2 (django, pygame). But I want to be
> excited about the future of the language. I understand the concept of
> needing to break backwards compatib
I am still living in the 2.x world because all the things I want to do
right now in python are in 2 (django, pygame). But I want to be
excited about the future of the language. I understand the concept of
needing to break backwards compatibility. But it's not particularly
exciting to think about. W
