New issue 3082: Migration from Bitbucket to ??? https://bitbucket.org/pypy/pypy/issues/3082/migration-from-bitbucket-to
Pierre Augier: As explained here [https://bitbucket.org/blog/sunsetting-mercurial-support-in-bitbucket](https://bitbucket.org/blog/sunsetting-mercurial-support-in-bitbucket), **Mercurial features and repositories will be officially removed from Bitbucket and its API on June 1, 2020.** I guess you thought about what to do for PyPy repository and PyPy development. I am also a Mercurial user and I am facing the same problem for some repositories. Thus, I am very interested to know what you plan to do. In particular, I am looking for a good forge for the Transonic project \([https://transonic.readthedocs.io](https://transonic.readthedocs.io)\), which by the way is compatible with PyPy3.6 \(currently only the nightly builds\) and could help a wider adoption of PyPy3 for projects using the Python scientific stack \(just by accelerating the numerical kernels using Numpy and let PyPy accelerate pure Python code\). I follow the Heptapod project [https://heptapod.net/](https://heptapod.net/) \(a friendly fork of GitLab to bring very good Mercurial support\). It seems to me that it starts to be nearly production ready and that it would nicely fit your workflow with Mercurial. Of course, it would be very convenient if a common instance \(free to use for simple users until a certain point\) could be setup \(something somehow similar to Github, but with Mercurial support\). Even for PyPy, it would be good in terms of visibility. I also heard that your repository would have to be fixed to be able to use Heptapod. What is the current status of these issues for PyPy? Have you already decided what to do? _______________________________________________ pypy-issue mailing list pypy-issue@python.org https://mail.python.org/mailman/listinfo/pypy-issue
