# Let's be more careful with planned removals **URL:** \ **Category:** Core Development\ **Created:** [June 19, 2023, 11:14am UTC](https://discuss.python.org/t/lets-be-more-careful-with-planned-removals/28109 "2023-06-19T11:14:14Z")\ **Posts on this page:** 1\ **Showing post:** 4
**Author:** ![vstinner](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/vstinner/32/15130_2.png) [@vstinner](https://discuss.python.org/u/vstinner)\ **Post date:** [June 19, 2023, 2:10pm UTC](https://discuss.python.org/t/lets-be-more-careful-with-planned-removals/28109/4 "2023-06-19T14:10:48Z")
Notes on the imp module removal. The imp removal was scheduled for a long time (the module was marked as deprecated and emitted a warning since Python 3.4), but it was blocked by pip (!): [Remove more deprecated importlib APIs from Python 3.12](https://github.com/python/cpython/issues/98040). It also took many years to remove the imp usage in the Python code base. Obviously, last bits were only updated to importlib recently. The [impact of imp removal (153 affected projects on PyPI top 5,000 projects)](https://github.com/python/cpython/pull/98573#issuecomment-1506919827) was known and taken in account in the decision. The imp removal was part of the larger change about the importlib module: [Meta issue for cleaning up import system cruft](https://github.com/python/cpython/issues/97850). There is now ongoing work to enhance the “update imp to importlib” documentation and helping affected projects: - [Improve the docs regarding the migration from imp to importlib · Issue #104212 · python/cpython · GitHub](https://github.com/python/cpython/issues/104212) - [Experience with Python 3.11 in Fedora](https://discuss.python.org/t/experience-with-python-3-11-in-fedora/12911) --- _[View the full topic](https://discuss.python.org/t/lets-be-more-careful-with-planned-removals/28109)._