Skip to content

Numpy version >= 1.10 dependency issue.  #4691

Closed

Description

@Erotemic

I'm working with a development version of numpy version 1.10.0.dev0-30d755d.

When trying to install matplotlib I get an error saying
error: numpy 1.10.0.dev0-30d755d is installed but numpy>=1.6 is required by set(['matplotlib'])

This is because 1.10 is registering as less than 1.6.

I'm not sure if this is fixed in the head repository, but this causes an issue when using current release on pip. Should be an easy fix. I just wanted to ensure people were aware of it.

Activity

  1. added this to the milestone on Jul 14, 2015
  2. added
    Release criticalFor bugs that make the library unusable (segfaults, incorrect plots, etc) and major regressions.
    on Jul 14, 2015
  3. tacaswell commented on Jul 14, 2015

    @tacaswell
    Member

    I feel this should be a bug against setuptools or pip?

  4. WeatherGod commented on Jul 14, 2015

    @WeatherGod
    Member

    It might be that your setuptools install needs to be updated to properly
    handle the new version numbering system.

    On Tue, Jul 14, 2015 at 11:54 AM, Thomas A Caswell <notifications@github.com

    wrote:

    I feel this should be a bug against setuptools or pip?

    —
    Reply to this email directly or view it on GitHub
    #4691 (comment)
    .

  5. jenshnielsen commented on Jul 15, 2015

    @jenshnielsen
    Member

    Normally this kind of thing happens when one uses string comparison to compare versions. However we are using LooseVersion in setupext.py which should work correctly.

  6. jenshnielsen commented on Jul 15, 2015

    @jenshnielsen
    Member

    I cannot reproduce this with numpy 1.10.0.dev0+49617ac and matplotlib master
    Python 3.4.3 setuptools 18.0.1 pip 7.1.0

    looseVersion is from distutils so it should be independent of setuptools/pip version unless setuptools does something funny

  7. added and removed
    Release criticalFor bugs that make the library unusable (segfaults, incorrect plots, etc) and major regressions.
    on Jul 15, 2015
  8. modified the milestones: , on Jul 15, 2015
  9. mdboom commented on Jul 15, 2015

    @mdboom
    Member

    And additionally, I don't think this error message even comes from matplotlib -- it's coming from pip.

  10. tacaswell commented on Jul 17, 2015

    @tacaswell
    Member

    I am now getting this too, but I think I have 1.9.2 installed via conda.

    Because I am feeling cranky, I assume this is fallout from merging #4668

  11. tacaswell commented on Jul 17, 2015

    @tacaswell
    Member

    although, both python setup.py develop and python setup.py install work for me, python setup.py test does not

  12. tacaswell commented on Jul 17, 2015

    @tacaswell
    Member

    I had a rouge install of numpy which 'pip remove numpy` fixed.

  13. tacaswell commented on Aug 30, 2015

    @tacaswell
    Member

    Closing as it is either a) a local configuration issue or b) bug in upstream tooling.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions