[TECH DEBT] DeprecationWarning: 'crypt' is deprecated and slated for removal in Python 3.13
Open
Nobody has claimed this yet.
tech-debt
- Dominant language
- Python
- Stars
- 15.7k
- Forks
- 5.6k
- Avg merge
- 2d 44m
- Merged PRs (30d)
- 80
Description
Description of the tech debt to be addressed, include links and screenshots
/usr/lib/python3.11/site-packages/salt/utils/pycrypto.py:26: DeprecationWarning: 'crypt' is deprecated and slated for removal in Python 3.13
import crypt
Versions Report
Salt Version:
Salt: 3006.1
Python Version:
Python: 3.11.3 (main, Apr 5 2023, 15:52:25) [GCC 12.2.1 20230201]
Dependency Versions:
cffi: 1.15.1
cherrypy: Not Installed
dateutil: 2.8.2
docker-py: Not Installed
gitdb: Not Installed
gitpython: Not Installed
Jinja2: 3.1.2
libgit2: Not Installed
looseversion: 1.1.2
M2Crypto: 0.38.0
Mako: 1.2.4
msgpack: 1.0.4
msgpack-pure: Not Installed
mysql-python: Not Installed
packaging: 23.0
pycparser: 2.21
pycrypto: Not Installed
pycryptodome: 3.12.0
pygit2: Not Installed
python-gnupg: Not Installed
PyYAML: 6.0
PyZMQ: 25.0.2
relenv: Not Installed
smmap: Not Installed
timelib: Not Installed
Tornado: 4.5.3
ZMQ: 4.3.4
System Versions:
dist: Arch Linux | Kernel: 6.3.1
locale: utf-8
machine: x86_64
release: 6.3.1-arch1-1
system: Linux
version: Arch Linux | Kernel: 6.3.1
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by inspecting salt/utils/pycrypto.py around the import crypt shown in the warning, then trace how that module uses it. Determine a supported replacement or compatibility approach that preserves the existing behavior and removes the Python 3.13 deprecation warning. Done means the warning no longer appears while the affected cryptographic functionality continues to work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- security
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100