You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
assignee='https://github.com/merwok'closed_at=<Date2014-03-13.02:30:03.503>created_at=<Date2012-03-12.23:22:49.587>labels= []
title='installing latest version of a project'updated_at=<Date2014-03-13.02:30:03.503>user='https://bugs.python.org/janjaapdriessen'
When you install a project for the first time and you don’t specify a version number, i.e. pysetup install spam, the latest version (or the latest final version (non-alpha/beta/rc), Alexis knows better) should be installed. This could be added to the docs.
If you later run “pysetup install "spam (X.Y)"” where X.Y is a higher version than what’s installed, then the project should be upgraded, unless it breaks other project’s dependencies (i.e. ham depends on spam < X.Y). There aren’t probably any tests for this.
If you have a version of spam installed and want to upgrade to the latest version that still satisfies other installed projects’ dependencies, without having to give a version number, (your request IIUC), then you could use a trick like “pysetup install "spam (< 99.99)"” (untested). However, I agree that “pysetup install --upgrade spam” is a better UI: it’s less kludgy and already familiar to pip and easy_install users.
merwok
changed the title
install latest version of a package
installing latest version of a project
Mar 12, 2012
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: