4 ms·
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/#
by 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 agoYep, 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 agoThis 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 agoFYI, the author of Flask was the same person who proposed and published the PEP on the byte str changes.