Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Django-simple-history v3.3.0 is reporting DeprecationWarning: pkg_resources is deprecated as an API with Django v3.2. #1238

Closed
bschollnick opened this issue Aug 28, 2023 · 2 comments

Comments

@bschollnick
Copy link

Describe the bug
Django-simple-history v3.3.0 is reporting DeprecationWarning: pkg_resources is deprecated as an API with Django v3.2.

../.venv/lib/python3.9/site-packages/simple_history/init.py:1
  /work/site1/.venv/lib/python3.9/site-packages/simple_history/init.py:1: DeprecationWarning: pkg_resources is deprecated as an API. See https://setuptools.pypa.io/en/latest/pkg_resources.html
    from pkg_resources import DistributionNotFound, get_distribution

We were on v3.0, and have upgraded, to eliminate Django41 warnings, since we are working to upgrade to Django v4.1.

Please note, I am seeing a v3.4 in the releases list, but pypi isn't showing that version as released?

To Reproduce

  1. pip install django-simple-history
  2. run our test pytest suite

Expected behavior
To not see Depreciation Warnings?

Environment (please complete the following information):

  • OS: Red Heat Enterprise 8
  • Python 3.9.16
  • Django 3.2.20
  • Django Simple History Version: 3.3.0
  • Database Version: "PostgreSQL 11.12 on x86_64-pc-linux-gnu, compiled by gcc (GCC) 4.8.5 20150623 (Red Hat 4.8.5-44), 64-bit"
@ddabble
Copy link
Member

ddabble commented Aug 29, 2023

Yes, this was resolved in v3.4.0, but that version has not yet been released to PyPI by the project leads. However, I just made a request to the Jazzband roadies to have it released, so I'm assuming it won't be long until it happens 🙂

@ddabble
Copy link
Member

ddabble commented Aug 29, 2023

Please reopen if it turns out that your issue was not resolved after all 😊

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants