-
Notifications
You must be signed in to change notification settings - Fork 194
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
nats-py[nkeys]
won't install on Python 3.12.0
#509
Comments
nats-py[nkeys]
won't install on Python 12nats-py[nkeys]
won't install on Python 3.12.0
This is a showstopper that needs urgent attention IMO |
yes, there will be a new release of nkeys with the replaced dependency this week |
Any update on this? |
@wallyqs This seems related to this other issue I filed in the nkeys repo nats-io/nkeys.py#10. If I force nkeys to point to the main branch of the git repo instead of pypi then this works (since it installs pynacl) |
Hey @wallyqs, it's been a few weeks since you promised the new release of nkeys. Can the community help in any way to make this happen soon? |
Someone raised this on Slack and I took a look. So it looks like what has happened here is that we have [edit: in the https://github.com/nats-io/nkeys.py repo] both a We're chasing this now. |
Looks like |
nkeys version with pynacl support has been released today: https://github.com/nats-io/nkeys.py/releases/tag/v0.2.0 |
Observed behavior
nats-py[nkeys]
has a dependency oned25519
, which errors on install:This is because
ed25519
usesversioneer
, which has a bug. There is an issue againsted25519
, but it seems to be a dead project.The right fix might be to move to
pynacl
, which does install on Python 3.12.Expected behavior
It should be possible to pull in
nkeys
on Python 3.12.Server and client version
Server and client versions don't matter.
I tested the latest
nats-py
release:pip install 'nats-py[nkeys]==2.4.0'
Host environment
Ubuntu 22.04, x86-64, pyenv used for Python 3.12.
Steps to reproduce
Install Python 3.12.0, then install
nats-py[nkeys]
The text was updated successfully, but these errors were encountered: