Hello Matti, I am having some troubles with the latest pypy and numpypy: basically, numpy.get_include() returns the wrong directory. I investigated a bit and I think the culprit are these two commits: https://bitbucket.org/pypy/pypy/commits/ad36a29d0fcc https://bitbucket.org/pypy/numpy/commits/26e09b343f Probably it's just a typo in the numpy commit, which specify '_numpy' instead of '_numpypy'. However, before committing the fix I wanted to ask you, to make sure I am not missing anything important :). ciao, Anto
Ok, thank you, I fixed&committed. About me being the first to report: actually, I think it's because there is a lot of confusion around about numpy+pypy. I started to investigate this because I saw by chance a colleague switching from installing numpypy to installing numpy. When I asked, he just said that his C extension did no longer work with numpypy on newer versions of PyPy. And as a result his code ran slower (because for his particular workload numpypy is better). So, lesson learnt: - people are confused about this numpy vs numpypy thing, Also, the fact that the numpypy repo is called "numpy" does not help, as they tend to think it's just an outdated copy of the offical numpy. - it's hard to find docs about this: the only docs I found are http://pypy.org/download.html which is not the first place I'd look at :) So: what is the current status of numpy vs numpypy? Is the latter still maintained or is it slowly dying? If numpypy is still relevant, I propose to hack things so that: 1) we have a dedicated page about numpy either on pypy.org or readthedocs 2) when you execute pip install numpy, it installs the upstream numpy but also displays a link to that page 3) pip install numpypy works as well (and displays the same link). What do you think? On Wed, Jan 18, 2017 at 9:05 PM, Matti Picus <matti.picus@gmail.com> wrote:
Hi Anto, On 19 January 2017 at 11:04, Antonio Cuni <anto.cuni@gmail.com> wrote:
- it's hard to find docs about this: the only docs I found are http://pypy.org/download.html which is not the first place I'd look at :)
Yes, I added this piece of doc recently. It was only a minimal attempt to fix the previously entirely undocumented state of the universe. And yes, definitely please document it more widely at places that make sense to someone that comes to PyPy with the intention to install numpy and no prior knowledge about the existence of such a double implementation. It would be cool to have some feedback from someone who actually works on pypy+numpy this time. :-) A bientôt, Armin.
Ok, thank you, I fixed&committed. About me being the first to report: actually, I think it's because there is a lot of confusion around about numpy+pypy. I started to investigate this because I saw by chance a colleague switching from installing numpypy to installing numpy. When I asked, he just said that his C extension did no longer work with numpypy on newer versions of PyPy. And as a result his code ran slower (because for his particular workload numpypy is better). So, lesson learnt: - people are confused about this numpy vs numpypy thing, Also, the fact that the numpypy repo is called "numpy" does not help, as they tend to think it's just an outdated copy of the offical numpy. - it's hard to find docs about this: the only docs I found are http://pypy.org/download.html which is not the first place I'd look at :) So: what is the current status of numpy vs numpypy? Is the latter still maintained or is it slowly dying? If numpypy is still relevant, I propose to hack things so that: 1) we have a dedicated page about numpy either on pypy.org or readthedocs 2) when you execute pip install numpy, it installs the upstream numpy but also displays a link to that page 3) pip install numpypy works as well (and displays the same link). What do you think? On Wed, Jan 18, 2017 at 9:05 PM, Matti Picus <matti.picus@gmail.com> wrote:
Hi Anto, On 19 January 2017 at 11:04, Antonio Cuni <anto.cuni@gmail.com> wrote:
- it's hard to find docs about this: the only docs I found are http://pypy.org/download.html which is not the first place I'd look at :)
Yes, I added this piece of doc recently. It was only a minimal attempt to fix the previously entirely undocumented state of the universe. And yes, definitely please document it more widely at places that make sense to someone that comes to PyPy with the intention to install numpy and no prior knowledge about the existence of such a double implementation. It would be cool to have some feedback from someone who actually works on pypy+numpy this time. :-) A bientôt, Armin.
participants (3)
-
Antonio Cuni -
Armin Rigo -
Matti Picus