Packaging issue with 0.7.0?
See original GitHub issueJust attempted to install the new release and saw the following in the output:
Requested django-salesforce==0.7.0 from https://pypi.python.org/packages/23/f5/5ccc55a19a4e6466d51ec245f993d11c8b74501d993c43a95d8d8e853081/django-salesforce-0.7.0.tar.gz#md5=f7d20defb0cd4aa9af4459a564b9af3a (from -r requirements.txt (line 89)), but installing version None
When I pip freeze
after installing, pip thinks the version is 0.6.9 still.
Issue Analytics
- State:
- Created 6 years ago
- Comments:6 (6 by maintainers)
Top Results From Across the Web
Bug in the 0.7.0 packaging · Issue #233 · encode/httpx · GitHub
I've tried to upgrade to 0.7.0 and it exploded with a $ poetry update Updating dependencies Resolving dependencies... (1.0s) Package operations: 0 installs, ......
Read more >All the New Things in {gt} 0.7.0 - RStudio
We are excited to demonstrate all the new things in gt 0.7.0. This release has so many new features and enhancements that unlock...
Read more >@xmldom/xmldom - npm Package Health Analysis | Snyk
Since version 0.7.0 this package is published to npm as @xmldom/xmldom and no longer as xmldom , because we are no longer able...
Read more >Issue uninstalling machine-wide ProvisionedAppX package
The issues arise when trying to uninstall the package for all users. ... Remove-AppPackage -AllUsers -package "DentalDialInstaller_3.0.7.0.
Read more >Build issue while packaging docker for openSUSE - Google Groups
Hello, I'm the docker's maintainer for openSUSE. While upgrading to 0.7.0 I decided to fix the build process used at packaging time (in...
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
I think the old Git stuff was at fault here, or something. I’ll be a lot more careful of subsequent releases; I ended up releasing 0.7.2 just to make sure the right version number was attached.
Ready by PR #185.
(Unfortunately, the issue 174 can not be closed yet.)