Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upClarify which part of the indexserver spec is deprecated #1357
Comments
|
I personally would like to remove it completely. I need to think what's a better solution to the problem though. I don't think it's tox problem to solve index server abstractions. People should use devpi for that with some option to pass in the index server via PIP_INDEX_URL env var. |
|
Having to pass in something rather than being able to configure it in the |
|
You can use setenv to set that env var in tox.ini. That's what we do at our company and works like a charm. |
|
I just tested it and I think |
|
One problem I just thought about is that you can't overwrite |
|
We can change the default pip command to auto pass through pip index URL from outside env var |
|
Here's what we use:
We should probably just make this as the default and drop the entire indexserver thing. This would keep the installer tool agnostic the index server selection. The main reason for this is that index server is a pip thing, conda/dpkg, for example, doesn't have such. It's a clearer separation of concern if we the tool doesn't know about pips internals; and makes it easier to extend to use other packaging tools. This allows the user to easily insert their own index server (such as a local devpi mirror index), but fallback to some hardcoded sane value on a per project basis. |
|
This needs a deprecation warning then and a hint how to solve this differently, plus some docs. |

Formed in 2009, the Archive Team (not to be confused with the archive.org Archive-It Team) is a rogue archivist collective dedicated to saving copies of rapidly dying or deleted websites for the sake of history and digital heritage. The group is 100% composed of volunteers and interested parties, and has expanded into a large amount of related projects for saving online and digital history.

... or even decide to not deprecate it after all.
This came up on the mailing list.
It seems that this config option is well established, works as expected and is used in many scenarios (especially corporate when using internal pypi repos with different stages or devpi). So we might want to decide to remove the deprecation notice completely, if there are no objections regarding the maintenance of it.
As @fschulze mentioned, at least the single index variant is highly desirable (and I am pretty sure widely used).
I would opt for removing the deprecation notice and keep the full functionality.