On Fri, Mar 26, 2021 at 10:37 PM Chris Angelico <ros...@gmail.com> wrote:
> On Sat, Mar 27, 2021 at 4:20 PM <pyt...@blackward.eu> wrote: > > By the way, some months ago I started trying to migrate to Python 3 and > > gave up in favor of creating said compilation. Compatibility of Python > > and its Packages decreased with V3 significantly. A whole lot of minor > > and major incompatibilities between your subversions and belonging > > packages. This was one reason, why Java took the route to its own death. > > FUD. Lots and lots of FUD. More reasons to not promote your > distribution. Use it if you will, but it doesn't merit any further > visibility. > Chris, not everything you dislike is anti-Python FUD. Dominik, if you want something like Python 2.7, you likely should try Tauthon or Pypy2. Don't expect pip to work well on Tauthon; last I heard that was not happening. Also Pypy2 has some issues with C extension modules, and I'm not confident it'll pip well either. It's very worthwhile to move to 3.x, but CPython has a rather sad compatibility story when it comes to C extension modules; hopefully CFFI is going to fix that in the long term. If you're avoiding porting pure Python code, then that feels to me a bit like foot dragging, as the pure Python changes are not that big and are pretty much limited to the 2.7 -> 3.0 transition. I like to build versions of Python from 0.9 to 3.10alpha, for the sake of quickly ascertaining what features were introduced in what versions of CPython. IOW, there are good reasons to keep around old Pythons. Python history is interesting. -- https://mail.python.org/mailman/listinfo/python-list