Hello, I would like to use the RPython toolchain in my project. The problem is, RPython is currently hidden inside PyPy and therefore not readily available. I found this thread https://mail.python.org/pipermail/pypy-dev/2012-October/010602.html which goes as far as to state "Note that the fact of splitting this is not up to discussion, however, how we go about it is.". So, what is the status of the splitting? Was this idea eventually abandoned?
On Tue, Apr 15, 2014, at 21:31, Bogdan Opanchuk wrote:
Hello,
I would like to use the RPython toolchain in my project. The problem is, RPython is currently hidden inside PyPy and therefore not readily available. I found this thread https://mail.python.org/pipermail/pypy-dev/2012-October/010602.html which goes as far as to state "Note that the fact of splitting this is not up to discussion, however, how we go about it is.". So, what is the status of the splitting? Was this idea eventually abandoned?
The RPython toolchain has been split. It's still in the same repo, though. See the toplevel rpython/ directory in the pypy checkout.
Hi Benjamin, Thank you, I've seen it in the repo. But one still cannot install it as a separate package, say, in CPython, and it's not even available as a package in the PyPy itself (it's only used at build stage, as far as I understand). Are there any plans to complete the splitting and make it a standalone package? On Wed, Apr 16, 2014 at 2:47 PM, Benjamin Peterson <benjamin@python.org> wrote:
On Tue, Apr 15, 2014, at 21:31, Bogdan Opanchuk wrote:
Hello,
I would like to use the RPython toolchain in my project. The problem is, RPython is currently hidden inside PyPy and therefore not readily available. I found this thread https://mail.python.org/pipermail/pypy-dev/2012-October/010602.html which goes as far as to state "Note that the fact of splitting this is not up to discussion, however, how we go about it is.". So, what is the status of the splitting? Was this idea eventually abandoned?
The RPython toolchain has been split. It's still in the same repo, though. See the toplevel rpython/ directory in the pypy checkout.
Hi Bogdan, On 16 April 2014 06:59, Bogdan Opanchuk <mantihor@gmail.com> wrote:
it's not even available as a package in the PyPy itself
What do you mean? "rpython" is the name of the top-level directory we're talking about, with "__init__.py" and everything. It is a regular package. A bientôt, Armin.
Hi Armin, It is a package, but it is not discoverable. I cannot install it with pip, and I cannot set it as a dependency for some other package. On Wed, Apr 16, 2014 at 6:45 PM, Armin Rigo <arigo@tunes.org> wrote:
Hi Bogdan,
On 16 April 2014 06:59, Bogdan Opanchuk <mantihor@gmail.com> wrote:
it's not even available as a package in the PyPy itself
What do you mean? "rpython" is the name of the top-level directory we're talking about, with "__init__.py" and everything. It is a regular package.
A bientôt,
Armin.
Bogdan: apologies, gmail, doesn't default to reply all and I forget sometimes.. msg: Bogdan, I just explicitly have pypy checked out somewhere and reference it with environment variables in my Makefile. It's not particularly nice, but it's really easy to get started on something and its kind of stuck for the duration of my project. https://github.com/samgiles/naulang/blob/master/Makefile Sam On Wed, Apr 16, 2014 at 10:00 AM, Bogdan Opanchuk <mantihor@gmail.com>wrote:
Hi Armin,
It is a package, but it is not discoverable. I cannot install it with pip, and I cannot set it as a dependency for some other package.
On Wed, Apr 16, 2014 at 6:45 PM, Armin Rigo <arigo@tunes.org> wrote:
Hi Bogdan,
On 16 April 2014 06:59, Bogdan Opanchuk <mantihor@gmail.com> wrote:
it's not even available as a package in the PyPy itself
What do you mean? "rpython" is the name of the top-level directory we're talking about, with "__init__.py" and everything. It is a regular package.
A bientôt,
Armin.
pypy-dev mailing list pypy-dev@python.org https://mail.python.org/mailman/listinfo/pypy-dev
Le 16/04/14 05:59, Bogdan Opanchuk a écrit :
Hi Benjamin,
Thank you, I've seen it in the repo. But one still cannot install it as a separate package, say, in CPython, and it's not even available as a package in the PyPy itself (it's only used at build stage, as far as I understand). Are there any plans to complete the splitting and make it a standalone package?
There are no firm plans, but it is still a goal. There are a few issues to solve first, though: * Unbundling pytest and py lib * Cleaning up and splitting the docs between PyPy and RPython * Deciding what to do with the repository
participants (5)
-
Armin Rigo -
Benjamin Peterson -
Bogdan Opanchuk -
Ronan Lamy -
Samuel Giles