Include globally configured repositories as fallback package sources

[abn]

• I have searched the issues of this repo and believe that this is not a duplicate.

Issue

As per current behavior, repositories added and configured via poetry config will not be used unless configured as sources within the project pyporject.toml file.

It would be useful, if we change the default behavior so as to make the second step is not mandatory. This would mean that a configured/added repository will be searched if the package is not available in any of the project specific sources prior to checking PyPI public repository.

An example, this is useful under CI/CD environments where controlled builds of dependent packages are required from a private repository without modifying checked out source.

[bjoernpollex]

I would go so far as to actually override the package repository. I use a local devpi server that mirrors PyPI, and ideally I want all requests to got through that.

[abn]

@bjoernpollex i reckon that should be a separate feature; ie. disable a repository by name or similar. In this particular case I'd want to check a private repository first and if that fails fetch the package from PyPI. This is especially useful when using patched builds that have not been released upstream yet.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[stale]

Closing this issue automatically because it has not had any activity since it has been marked as stale. If you think it is still relevant and should be addressed, feel free to open a new one.

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.