4 ms·

2.6–3.3

• SiVal 14y ago
  Woo hoo! If you don't mind a suggestion, you might add that fact to your feature list. It can hardly be taken for granted and is a very important feature to those who are already past their legacy upgrade hurdles.
• TorKlingberg 14y ago
  If you can share some advice on Python 2/3 compatibility that would we very interesting. Especially things related to Unicode and testing. I see you have a single codebase for both versions. That is the same approach I took with my (much smaller) library, but several people advised against it. I also see you have very few "from __future__ import ..." Is that a conscious decision? In any case, thank you! I will use Requests as an example to follow.
  • tshepang 14y ago
    Using a single codebase for both Python 2 and 3 seems the most fashionable thing these days. It is, after all, the approach followed by Pyramid and Django. I also think it makes maintenance easier. The __future__ import is a consequence of it.