Skip to content

Write Patch for setuptools and distribute / easy_install #23

pedersen opened this Issue Sep 24, 2012 · 4 comments

2 participants

TurboGears member

This issue existed on SourceForge. The original can be viewed at

TurboGears member

Original Author: pedersen, Original Timestamp: 2011-12-18 04:41:55.493000

Original Body: This is a ticket that really belongs on other trackers, but it's of use to us specifically, so I'm noting it in our tracker.

easy_install will not, by default, use our index. We have to create a command line guide for users in order for it to work.

It would be nice if we could update easy_install in such a way that our script could say "this is where our package index lives, use it only".

Furthermore, easy_install should only process that option on the first package it installs. This way, if somebody uses "easy_install tg.devtools", it will download from PyPI, run the installer, and then stash away the new option, using it for subsequent packages, but ignoring that option if it appears in subsequent packages.

This would allow people to develop their own package, their own package index, and have their package refer to that without worry about what will happen when one of those packages has the option set. For example, if a developer makes a package that relies on tg.devtools, and also has a bunch of other packages, they should not be worried that their package will be uninstallable if the machine installing it is stuck behind a proxy and cannot reach the internet, only a local intranet.

I have a feeling this description is not complete, but it should help to steer a discussion in the right direction when this patch is developed.

TurboGears member

Original Author: *anonymous, Original Timestamp: 2011-12-18 11:07:18.118000

Original Body: Discussing this on mailing list might help, maybe something like this is already possible.

TurboGears member

Original Author: pedersen, Original Timestamp: 2012-08-24 01:31:27.451000

Original Body: - version: 2.1.4 --> 2.1.5

  • milestone: 2.2.0 --> 2.3.0
TurboGears member
amol- commented Jan 14, 2014

This is not required anymore since TurboGears can now be installed directly from PyPi.

@amol- amol- closed this Jan 14, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.