Django contrib module removed in 0.14.0 but still packaged in the wheel
See original GitHub issueI noticed that the 0.14.0 release removed ariadne.contrib.django
, but that module is still packaged as part of the wheel on PyPI. It doesn’t seem to be present in the sdist uploaded PyPI, though (as expected). Not a big deal, but it led to some brief confusion when comparing a local copy of 0.14.0 with the tagged version on github.
Issue Analytics
- State:
- Created 2 years ago
- Reactions:2
- Comments:7 (4 by maintainers)
Top Results From Across the Web
No module named 'django.contrib.wagtail' - python
I dropped the database and created a new one in pgAdmin and executed python manage.py makemigrations and python manage.py migrate - Both worked....
Read more >Change Log — Django DDP 0.19.1 documentation
Consistent handling of client errors ( MeteorError ) which shouldn't be logged. Reduce wheel size from 204KB to 68KB by removing dddp.test package....
Read more >Django Deprecation Timeline
This document outlines when various pieces of Django will be removed or altered in a backward incompatible way, following their deprecation, as per...
Read more >modulenotfounderror: no module named 'bootstrap5' - You.com
i'm trying to integrate payments subscription with Paystack using Django but it's throws me an error every time i do /manage.py runserver. the...
Read more >pipenv Documentation - Read the Docs
This tutorial walks you through installing and using Python packages. ... :func:django.contrib.auth.views.login and :doc:i18n </topics/i18n/index>).
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Yeah, looks like it was there in build dir when I’ve ran twine. I’ll release 0.14.1 sometime next week to resolve this.
This is fine, but if you wish to get your point across, you can’t do it aggressively. This is OS project and nobody here has to put up with it.
I also need to point out that Semver brings up two things: BC changes should bump major (so we should be at 2.0 now) and that zero-releases are effectively free-for-all. That last point + fact this change was announced for over a year was actually why I’ve decided to carry on with 0.14.1 here.
It’s shame that this broke your project, and I’m sorry for the inconvenience (and I’ll try do better next time 🤞), but your OP was completely uncalled for.