# Packaging and Python 2

**URL:** <https://discuss.python.org/t/packaging-and-python-2/662>\
**Category:** Packaging\
**Created:** [January 11, 2019, 4:07am UTC](https://discuss.python.org/t/packaging-and-python-2/662 "2019-01-11T04:07:43Z")\
**Posts on this page:** 1\
**Showing post:** 79

<div class="post-metadata">

**Author:** ![Julian](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/julian/32/1277_2.png) [@Julian](https://discuss.python.org/u/Julian)\
**Post date:** [January 27, 2019, 11:53pm UTC](https://discuss.python.org/t/packaging-and-python-2/662/79 "2019-01-27T23:53:28Z")

</div>

I’ve only just found this discussion, but yes, PyPy has no Py2 EOL plans currently (and I can say for us $WORK-wise, we have no real plans to move to PyPy3 until it is a bit more mature, and until we run extensive benchmarking showing performance is close to equal, so we’re certainly at least a year or two away).

Obviously those of us who use it are still using `pip` today, so continuing py2 support is certainly in my interests, but I obviously understand the desire to drop it from a maintenance perspective…

---

_[View the full topic](https://discuss.python.org/t/packaging-and-python-2/662)._