Hi Dima, On Wed, Feb 02, 2022 at 11:11:31AM +0900, Dima Tisnek wrote:
> #1 PyPy must track Python language versions (and CPython stdlib versions) > > You've released 7.3.8 with 3.8 support and I already use [Python > language version] 3.9 in production and 3.10 in CI. [...] > Ideally PyPy would track these in lock-step (released at the same > time); an acceptable compromise may be a 3-month delay. Most people do not track the latest Python. They use their vendor's Python, which may be a number of releases back, or even whatever legacy version their application is written for. For example, there are still people using Python 2.7 https://access.redhat.com/solutions/4455511 and the default version of Python that ships with RHEL 8 is changing from 3.6 to 3.8. Not everyone moves fast to the latest version of the language. For some people stability is more valuable than features. I'm sure that the PyPy devs would support 3.11 if they had the manpower. Did you think that they just hadn't noticed that CPython was up to 3.10 and 3.11 is in development? > #2 Move to GitHub already. Your current repo setup makes it impossible > for the majority to of developers to contribute. "Impossible"? Like you literally cannot get your head around a different repo than GitHub? How will you cope if your job requires you to learn new skills? Or even a new language? > performance comes second. That's a strange thing to say to a Python interpreter whose reason for existence is to improve performance. -- Steve _______________________________________________ pypy-dev mailing list pypy-dev@python.org https://mail.python.org/mailman/listinfo/pypy-dev
