Upgrade package tooling, drop Django<3.2, DjangoCMS<3.9 and Python<3.9#34
Upgrade package tooling, drop Django<3.2, DjangoCMS<3.9 and Python<3.9#34
Conversation
|
This pull request sets up GitHub code scanning for this repository. Once the scans have completed and the checks have passed, the analysis results for this pull request branch will appear on this overview. Once you merge this pull request, the 'Security' tab will show more code scanning analysis results (for example, for the default branch). Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results. For more information about GitHub code scanning, check out the documentation. |
protoroto
force-pushed
the
feature/issue-33-upgrade-package
branch
from
6f17187 to
6b8e6f1
Compare
| [options] | ||
| include_package_data = True | ||
| install_requires = | ||
| django-multisite |
There was a problem hiding this comment.
this PR requires an upgraded version of django-multisite and we must decide how to go forward
There was a problem hiding this comment.
@yakky Do you have any update on this? Unfortunately it looks like django-multisite is not being updated anymore.
4 participants
Description
Upgrade package tooling, drop Django<3.2, DjangoCMS<3.9 and Python<3.9
Notes
Fix #33