Drop support for Python 2.7?
Opened this issue · 2 comments
Hello @Qix-.
So, to explain you the problem I'm facing: I have implemented a few fixes for some edge cases, but I'm not sure how to handle it properly for Python 2.7.
These fixes implies working with strings formatting and encoding, which is a pain to deal with in Python 2.
Considering that official Python 2 support is ending in less than one year, what are your thoughts on tagging better_exceptions v0.2.2 as the "final" stable release for Python 2, and making v0.3.0 Python 3 only?
If you wish to maintain compatibility for Python 2.7, I think I could manage to make it work for all versions. But I'm afraid that it will clutter the codebase while introducing prone to errors string manipulations. This is why I prefer to ask you first: does it worth it?
Didn't think it would ever happen.
Yes, I think this is a good idea. I'd go so far as making v1 python 3 only.
@Qix- Glad to hear that. ❤️
How do you want to handle the transition?
For now I created a new python3_only branch on top of which I will open pull requests for my fixes. Except if you prefer this to be managed by master directly.