Page 2 of 2 FirstFirst 12
Results 11 to 17 of 17

Thread: Python 3.4 Is Now Available With New Features

  1. #11
    Join Date
    Aug 2008
    Location
    Finland
    Posts
    1,577

    Default

    Quote Originally Posted by kaprikawn View Post
    I just stick to Perl now.
    Yes, because Perl6 has been such an easy migration.

  2. #12
    Join Date
    Dec 2010
    Location
    MA, USA
    Posts
    1,211

    Default

    I personally use python 3 regularly, along with Qt5 and a few other libraries. I'm pretty indifferent about the usage of each, and I simply don't care about the libraries that don't work in python 3. Considering most of the important libraries have already made the switch, I'd suggest other developers to move to 3 when they get the chance.

    Also, it's surprisingly easy to switch. I had roughly 3000 lines of code written in python 2 and only had to change maybe 10 lines to make it work in python 3.

    So far the only thing I don't like about python 3 is it seems a lot more picky about string encoding, where even C is sometimes simpler.

  3. #13
    Join Date
    Sep 2013
    Posts
    125

    Default

    Quote Originally Posted by schmidtbag View Post
    So far the only thing I don't like about python 3 is it seems a lot more picky about string encoding, where even C is sometimes simpler.
    My experience is that Python 3 makes working with strings and encodings simpler. While you can find the rare case where every string being unicode can make things more difficult, for most purposes this is an improvement over Python 2.

  4. #14
    Join Date
    Apr 2013
    Posts
    90

    Default

    At work we have around three web apps using Python 3 already (from 3.3 up). Only the last one started on Python 3.3, and the first two were ported to this version. That required some noticeable amount of pull requests to packages found in the requirements (but usually it was like exception syntax, or print - fixable in few lines). Some more complex apps/libraries are still Python 2 only so not everything can work with 3.X yet.

  5. #15
    Join Date
    Dec 2010
    Location
    MA, USA
    Posts
    1,211

    Default

    Quote Originally Posted by tuubi View Post
    My experience is that Python 3 makes working with strings and encodings simpler. While you can find the rare case where every string being unicode can make things more difficult, for most purposes this is an improvement over Python 2.
    Yes, encoding/decoding may be simpler, but in python 2 you rarely had the need to even deal with encoding in the first place. Regardless, it isn't really a big deal to me, just a little tedious at times (in comparison).

  6. #16
    Join Date
    Sep 2013
    Posts
    125

    Default

    Quote Originally Posted by schmidtbag View Post
    Yes, encoding/decoding may be simpler, but in python 2 you rarely had the need to even deal with encoding in the first place.
    Well, that may be the case if your users speak a language with an alphabet covered by ASCII. I've had to deal with encoding in pretty much every single project we've done. English isn't the only language most of us need to deal with.

  7. #17
    Join Date
    Sep 2011
    Posts
    62

    Default

    Quote Originally Posted by kaprikawn View Post
    It's a while since I looked at Python. Is everyone still ignoring the version 3.x branch in favour of writing 2.x version code because thet can't be bothered to update their code or because of modules that only support 2.x?
    Most major/important libraries are available for Python 3 now:

    http://python3wos.appspot.com/

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •