Closed dazza-codes closed 5 years ago
Should have been fixed in https://github.com/eventbrite/invoke-release/commit/764712d7abf31d26504ca49d3c3c99b071bf0c64 but apparently not? Or that change is not yet released to pypi?
This might be a pipenv
issue when creating a new virtualenv - it may not parse any restrictions on wheel
versions in the Pipfile
dependency graph before installing the latest version of wheel in a new virtualenv. It could be related to using pipenv install
without the --dev
option when creating the new virtualenv.
This seems to be easily fixed by reinstalling the pipenv:
$ pipenv --rm
$ pipenv install --dev
$ pipenv shell
$ wheel version
wheel 0.31.1
To be sure, the problem can be replicated when recreating the pipenv virtualenv without installing the dev-dependencies, i.e.
$ pipenv --rm
$ pipenv install # without --dev option
$ pipenv shell
$ wheel version
wheel 0.32.3
Add the following to Pipfile
[dev-packages]
:
wheel = "~=0.31.0" # invoke needs wheel.archive
Until there is an updated release of either invoke
and/or invoke-release
that works without the archive
component of wheel.
Raised by https://github.com/eventbrite/invoke-release/blob/master/python/invoke_release/tasks.py#L16