Coder Social home page Coder Social logo

Comments (6)

taldcroft avatar taldcroft commented on May 24, 2024

I saw this too. I think that the setup process does something like rewriting _version.py. AFAIK right now you can't run sherpa in place, it needs to be installed.

from sherpa.

cdeil avatar cdeil commented on May 24, 2024

@taldcroft – Thanks for confirming the issue.
For me python setup.py install doesn't work because of issue #15.

from sherpa.

olaurino avatar olaurino commented on May 24, 2024

I recently upgraded the versioneer code because of some issues with PEP440, but then I didn't upgrade the relative files. I'll create a PR with the required changes. Thanks for reporting this.

from sherpa.

olaurino avatar olaurino commented on May 24, 2024

By the way, the versioneer is in place to make sure that when reporting a bug, a simple python setup.py version allows users to pinpoint the version of sherpa they are using. If it is a release, then it will be the release version (git tag), otherwise we can tell exactly what commit was used to build Sherpa, and even if the working tree is dirty (i.e. there were uncommitted changes when sherpa was built).

from sherpa.

olaurino avatar olaurino commented on May 24, 2024

@cdeil for some strange reason we cannot reproduce this issue anymore, so we cannot test whether PR #21 actually fixes it or not.

Could you please confirm that: a) you can still reproduce the issue from the master branch with a clean working tree, and b) PR #21 actually solves the issue.

Thanks.

from sherpa.

DougBurke avatar DougBurke commented on May 24, 2024

So, I can now replicate this error by starting ipython from within the top-level sherpa directory (that is, the one that contains setup.py, and fits in with the comments above that Sherpa is not yet able to be run in place). In this case a

from sherpa.astro import ui

call will raise the NameError. With PR #21 I no longer get this error; instead I get the error message ImportError: No module named _utils from the line from sherpa.utils._utils import * in sherpa/utils/__init__.py. So, it looks like PR #21 fixes the reported problem but there's still more to do with getting it to work - which is being tracked in bug #14.

Note that in both cases (using master or PR #21), I can import sherpa as long as I start the python/ipython from outside the Sherpa tree.

from sherpa.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.