4 ms·

What's the latest on Python 3 support in Flask? Edit: Why the downvote? I'm just fishing for anybody having newer info than what's on the website out of genuin

by sho_hn 14y ago

What's the latest on Python 3 support in Flask? Edit: Why the downvote? I'm just fishing for anybody having newer info than what's on the website out of genuine interest and because HN tends to be a place where people would know; it's not meant as a troll.

uvtc 14y ago
I'm guessing that this section of the docs http://flask.pocoo.org/docs/advanced_foreword/#the-status-of-python-3 http://flask.pocoo.org/docs/advanced_foreword/#the-status-of... will get updated once the status changes.
- sho_hn 14y ago
  Yep, I read that, and was e.g. wondering whether the upcoming 3.3 did anything to address the issues alluded to there. Basically, it's a developing situation and it's not economical to change that text for every inch things move, but I'd love to hear what's in flight right now in this less formal context.
- batista 14y ago
  This very section is that worries me. Nobody ever bothered updating it, not when the relevant WSGI spec came out, and not when Python 3.3 announced the byte str changes that would help. If even Django and Pyramid can have a 3 roadmap --and even implementation--, surely Flask could too. Seems like they just dont bother, so they put it in the backburner. Which is mighty fine, its a volunteer project after all, but I find said document misinforming, to say the least.
  - chrismsnz 14y ago
    FYI, the author of Flask was the same person who proposed and published the PEP on the byte str changes.
deleted 14y ago
[deleted]
hoodoof 14y ago
Python 2 is starting to smell very "legacy" and stuff that isn't moving to Python 3 is starting to look less relevant.
- scott_w 14y ago
  Considering that some of the most common libraries aren't on Python 3, I'd hardly call Python 2 "legacy". Until the libraries you need at least support Python 3, it's not worth even starting to move across.
  - hoodoof 14y ago
    That's an old wives tale that is getting older by the day. People like to roll that excuse out not to move to Python 3 and it may have been true in the past but there are now enough libraries available to get most stuff done in Python3. It is true that the laggards are starting to look like the are living in the past. Python3 was released 3.5 years ago and is getting a real head of steam. Projects that don't move over will eventually get replaced entirely by projects that have either moved to, or been created onl for, Python3. This old "the libraries aren't available for Python3" story is a legacy story too and just sounds like an excuse.
    - scott_w 14y ago
      The most-used web framework not supporting Python 3 is just an old wives' tale? https://www.djangoproject.com/weblog/2012/mar/13/py3k/ https://www.djangoproject.com/weblog/2012/mar/13/py3k/ Even in 1.5, Django's Python 3 support will be "experimental". This, quite simply, takes Python 3 off the table for the foreseeable future. The major Linux distributions (Ubuntu, Fedora) aren't aiming for full Python 3 support until 2014 which. The core Python team themselves aren't expecting Python 3 usage to take off until 2014 either. In real-world usage, we can't all just drop all the libraries we're using and switch over to another because "it's new".
      - hoodoof 14y ago
        Exactly my point. Projects that don't make the transition risk being perceived as legacy and irrelevant. There is real opportunity here for new solutions that embrace the new rather than stoically stay in the old.

by sho_hn 14y ago

uvtc 14y ago

I'm guessing that this section of the docs http://flask.pocoo.org/docs/advanced_foreword/#the-status-of-python-3 http://flask.pocoo.org/docs/advanced_foreword/#the-status-of... will get updated once the status changes.

sho_hn 14y ago
Yep, I read that, and was e.g. wondering whether the upcoming 3.3 did anything to address the issues alluded to there. Basically, it's a developing situation and it's not economical to change that text for every inch things move, but I'd love to hear what's in flight right now in this less formal context.
batista 14y ago
This very section is that worries me. Nobody ever bothered updating it, not when the relevant WSGI spec came out, and not when Python 3.3 announced the byte str changes that would help. If even Django and Pyramid can have a 3 roadmap --and even implementation--, surely Flask could too. Seems like they just dont bother, so they put it in the backburner. Which is mighty fine, its a volunteer project after all, but I find said document misinforming, to say the least.
- chrismsnz 14y ago
  FYI, the author of Flask was the same person who proposed and published the PEP on the byte str changes.

deleted 14y ago

[deleted]

hoodoof 14y ago

Python 2 is starting to smell very "legacy" and stuff that isn't moving to Python 3 is starting to look less relevant.

scott_w 14y ago
Considering that some of the most common libraries aren't on Python 3, I'd hardly call Python 2 "legacy". Until the libraries you need at least support Python 3, it's not worth even starting to move across.
- hoodoof 14y ago
  That's an old wives tale that is getting older by the day. People like to roll that excuse out not to move to Python 3 and it may have been true in the past but there are now enough libraries available to get most stuff done in Python3. It is true that the laggards are starting to look like the are living in the past. Python3 was released 3.5 years ago and is getting a real head of steam. Projects that don't move over will eventually get replaced entirely by projects that have either moved to, or been created onl for, Python3. This old "the libraries aren't available for Python3" story is a legacy story too and just sounds like an excuse.
  - scott_w 14y ago
    The most-used web framework not supporting Python 3 is just an old wives' tale? https://www.djangoproject.com/weblog/2012/mar/13/py3k/ https://www.djangoproject.com/weblog/2012/mar/13/py3k/ Even in 1.5, Django's Python 3 support will be "experimental". This, quite simply, takes Python 3 off the table for the foreseeable future. The major Linux distributions (Ubuntu, Fedora) aren't aiming for full Python 3 support until 2014 which. The core Python team themselves aren't expecting Python 3 usage to take off until 2014 either. In real-world usage, we can't all just drop all the libraries we're using and switch over to another because "it's new".
    - hoodoof 14y ago
      Exactly my point. Projects that don't make the transition risk being perceived as legacy and irrelevant. There is real opportunity here for new solutions that embrace the new rather than stoically stay in the old.