Open gregoryfoster opened 10 months ago
Hey @gregoryfoster! Thanks for giving this a try! Sorry it isn't working for you.
I think the most obvious answer might be that we simply haven't released a new version in a while and the package install is limited to py310. If you try downgrading to 3.10 let me know if it works please.
Although, I don't know why that would install all the way back to 0.0.2
...
The only other thing to try would be to follow our install process in CI definition as I just ran a new CI job and it all worked fine: https://github.com/CouncilDataProject/speakerbox/actions/runs/6882586499/job/18721399373
P.S. I will respond to your email right now!
After installing pyenv
to manage Python environments, upgrading pipenv
, and installing a new Python 3.10.13 virtual environment, I'm still seeing the same unusual behavior.
However, this does not appear to be an issue when using pip
as it pulled the correct version when run outside of a virtual environment. So I've reconfigured this issue as specific to pipenv
. Probably something specific to my environment, but leaving this open for now.
Describe the Bug
When attempting an installation of the module, version 0.0.2 is installed by default.
Expected Behavior
PyPI has all of the versions, not sure why this version would be selected.
Reproduction
pipenv install speakerbox
Environment