Tzu-ping Chung d45541c8f3 Skip candidate not providing valid metadata ... This is done by catching InstallationError from the underlying distribution preparation logic. There are three cases to catch: 1. Candidates from indexes. These are simply ignored since we can potentially satisfy the requirement with other candidates. 2. Candidates from URLs with a dist name (PEP 508 or #egg=). A new UnsatisfiableRequirement class is introduced to represent this; it is like an ExplicitRequirement without an underlying candidate. As the name suggests, an instance of this can never be satisfied, and will cause eventual backtracking. 3. Candidates from URLs without a dist name. This is only possible for top-level user requirements, and no recourse is possible for them. So we error out eagerly. The InstallationError raised during distribution preparation is cached in the factory, like successfully prepared candidates, since we don't want to repeatedly try to build a candidate if we already know it'd fail. Plus pip's preparation logic also does not allow packages to be built multiple times anyway.		2020-12-12 02:23:32 +08:00
..
data	Add integration tests for experimental feature fast-deps	2020-07-21 16:00:34 +07:00
functional	Skip candidate not providing valid metadata	2020-12-12 02:23:32 +08:00
lib	Add a better error message for no-more-responses	2020-10-30 23:08:59 +05:30
unit	Skip candidate not providing valid metadata	2020-12-12 02:23:32 +08:00
yaml	Update YAML tests for resolver changes	2020-10-30 23:08:47 +05:30
__init__.py	Port to Python3	2011-03-15 15:49:48 -04:00
conftest.py	Update tests for resolver changes	2020-10-30 23:08:31 +05:30