Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

pip install numpy pyastronomy fails. #22

Closed
jason-neal opened this issue Apr 24, 2017 · 1 comment
Closed

pip install numpy pyastronomy fails. #22

jason-neal opened this issue Apr 24, 2017 · 1 comment

Comments

@jason-neal
Copy link
Contributor

jason-neal commented Apr 24, 2017

The main issue is
pypa/pip#25
but it is a fairly common issue.

In a new environment

pip install numpy pyastronomy
Collecting numpy
  Downloading numpy-1.12.1-cp35-cp35m-manylinux1_x86_64.whl (16.8MB)
    100% |████████████████████████████████| 16.8MB 1.8MB/s 
Collecting pyastronomy
  Downloading PyAstronomy-0.10.1.tar.gz (617kB)
    100% |████████████████████████████████| 624kB 2.2MB/s 
    Complete output from command python setup.py egg_info:
    Please install 'numpy' first.
    Traceback (most recent call last):
      File "<string>", line 1, in <module>
      File "/tmp/jneal/pip-build-r24zffou/pyastronomy/setup.py", line 153, in <module>
        class WithExtCommand(Command):
    NameError: name 'Command' is not defined
    
    ----------------------------------------
Command "python setup.py egg_info" failed with error code 1 in /tmp/jneal/pip-build-r24zffou/pyastronomy/

Basically scipy/scipy#453 contains the PR of how they resolved this issue for scipy which I quote.

It was failing because of the pre installation request from pip to ./setup.py egg_info (which is perfectly valid request and shouldn't fail), before numpy actually was installed.

Fix is straightforward - not to use numpy for commands that are not connected with build and install.

The main reason this affects me is I want to include pyastronomy into a requirements.txt file along with numpy. pip downloads and setups all before starting to install.

@sczesla
Copy link
Owner

sczesla commented May 29, 2017

Hi,
I modified setup.py and uploaded a new release 0.11.0 to pypi. According to my tests, this resolves the issue.
Cheers, Stefan

@sczesla sczesla closed this as completed May 29, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants