# Draft PEP: The "local" wheel tag

**URL:** <https://discuss.python.org/t/draft-pep-the-local-wheel-tag/3145>\
**Category:** Packaging\
**Created:** [February 8, 2020, 6:50am UTC](https://discuss.python.org/t/draft-pep-the-local-wheel-tag/3145 "2020-02-08T06:50:20Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![pf\_moore](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/pf_moore/32/35_2.png) [@pf\_moore](https://discuss.python.org/u/pf_moore)\
**Post date:** [February 8, 2020, 12:36pm UTC](https://discuss.python.org/t/draft-pep-the-local-wheel-tag/3145/3 "2020-02-08T12:36:10Z")

</div>

> [@steve.dower](#):
>
> If the underlying issue is just “pip prefers PyPI wheels over wheels in its cache,”

The issue (if indeed it is an issue) is that pip doesn’t guarantee _any_ preference, and we don’t really want to start doing so. The principle that _any_ compatible distribution file for version X.Y of package A should be equally usable is important (IMO) - it’s behind things like the resolution algorithm, dependency specifications, etc. Once we start saying that A version X.Y from index I is “better” than A version X.Y from index J, then we add a whole new dimension to the dependency resolution process.

---

_[View the full topic](https://discuss.python.org/t/draft-pep-the-local-wheel-tag/3145)._