Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

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.



FYI, the author of Flask was the same person who proposed and published the PEP on the byte str changes.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: