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 issues #18

Open
onaclov2000 opened this issue Nov 18, 2015 · 1 comment
Open

pip install issues #18

onaclov2000 opened this issue Nov 18, 2015 · 1 comment

Comments

@onaclov2000
Copy link

I'm fairly unfamiliar with how pip works, however I guess the newer versions only allow installing of certain release number formats. so the default "pip install <>" isn't working.
This SO question/answer talks about the format/convention that is necessary for the newer pip installs.

http://stackoverflow.com/questions/18230956/could-not-find-a-version-that-satisfies-the-requirement-pytz

Pre-release Versions

Starting with v1.4, pip will only install stable versions as specified by PEP426 by default. If a version cannot be parsed as a compliant PEP426 version then it is assumed to be a pre-release.

If a Requirement specifier includes a pre-release or development version (e.g. >=0.0.dev0) then pip will allow pre-release and development versions for that requirement. This does not include the != flag.

The pip install command also supports a --pre flag that will enable installing pre-releases and development releases.

So I finally tried

pip install --pre pymdptoolbox 

and it worked

@onaclov2000
Copy link
Author

I'm not sure if an update to the "how to install" is in order, or the pip name format needs updating

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

1 participant