Skip to content

no module named version in setup.py #54

Closed

Description

@wkerzendorf

Hi Guys,

I fetched from upstream (just now) and it seemed to have started out in the right direction, but then met an unfortunate end:

python setup.py develop
Downloading http://pypi.python.org/packages/source/d/distribute/distribute-0.6.19.tar.gz
Extracting in /var/folders/zc/cbprg2bj1l50c3y6sfzf64wm0000gn/T/tmpXuKWeL
Now working in /var/folders/zc/cbprg2bj1l50c3y6sfzf64wm0000gn/T/tmpXuKWeL/distribute-0.6.19
Building a Distribute egg in /Users/wkerzend/scripts/python/astropy
/Users/wkerzend/scripts/python/astropy/distribute-0.6.19-py2.7.egg
Traceback (most recent call last):
  File "setup.py", line 13, in <module>
    import astropy
  File "/Users/wkerzend/scripts/python/astropy/astropy/__init__.py", line 3, in <module>
    from astropy.version import version as __version__
ImportError: No module named version

I have never tried python setup.py develop before but I heard it somehow sets the package path so I can continue to developing while my astropy is in its place.

Cheers
Wolfgang

Activity

  1. eteq commented on Nov 7, 2011

    @eteq
    Member

    Are you sure you're actually on the upstream version? The error you're indicating here was present in a much older version but was fixed a while back (unless it has returned...) - and it looks like your fork is about a month old... if you do get show HEAD, what does it give you?

  2. wkerzendorf commented on Nov 7, 2011

    @wkerzendorf
    MemberAuthor

    you are right!. But I did do a git fetch upstream. hmm..
    Merge: fe1481a 782d606
    Author: Erik Tollerud [email protected]
    Date: Fri Oct 7 11:18:58 2011 -0700

    Merge pull request #7 from astrofrog/clean-layout
    
    Tidies up package to be PEP8 compliant and fixes a few typos.
    
  3. eteq commented on Nov 7, 2011

    @eteq
    Member

    git fetch upstream doesn't update the local source code - it just retrieves it from the server for later use. you want to do git pull upstream master (or git fetch upstream followed by git merge upstream/master - basically the same thing). After that, if you want it to be reflected in yout fork on github, do git push origin master (or maybe just git push depending on how you set things up)

  4. wkerzendorf commented on Nov 7, 2011

    @wkerzendorf
    MemberAuthor

    yes I got that now worked out.

    Thanks!

  5. added a commit that references this issue on Jan 23, 2015
  6. added a commit that references this issue on Nov 9, 2015
  7. added a commit that references this issue on Jul 2, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions