have a private _compat module to not depend on a specifc flask version #64
Conversation
|
now that we have py3 compatible pocoo stuff released, could someone please check what's the problem with this, so that we can also have a py3 compatible flask-script release soon? |
|
Sorry for the lack of updates, I've been busy with work and other personal projects. There is still 1 failing test in Python 3.3 in the python3 branch that needs to be resolved. I have some changes locally I haven't pushed yet. I've spent a few evenings attempting to fix this but haven't yet (there appears to be some difference with python 3.x vs 2.x with argparse and I haven't merged in your PR yet as I wanted to get a working build on all platforms first. |
|
Ah, right, now I remember... Yeah, I tried also to fix that, but couldn't quickly find the root cause of that remaining issue. But, just as a suggestion: as long as there is no issue on python 2.x platforms, you could merge it without regression. Of course, before officially announcing/releasing 3.3 support, it has to get fixed. |
|
True. I wouldn't like to get the python3 branch merged even without python 3.3 support just to get more people looking at it. There is also an open issue (#63) that is fixed but needs a release to PyPI. I'll look at least getting everything ready for a 2.x release and hopefully get 3.x fixed soon. |
|
Manually merged - 0df2124 |
No description provided.