-
Notifications
You must be signed in to change notification settings - Fork 256
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
Python 3 support #474
Comments
This is being worked on! Expect to see it in a day or two, it’s just about
complete — we are also dropping support for Python 2 and switching
completely over to Python 3.
On Sun, Sep 22, 2019 at 9:29 AM Roman Yurchak ***@***.***> wrote:
Thanks for this library!
Just a reminder that most major scientific Python packages have dropped
Python 2 support now, so only supporting Python 2 is quite problematic.
Related to #110 <#110>
There was a WIP attempt in #132
<#132> that didn't receive much
interest.
Is the Python 3 migration something you expect to happen? Any help needed
there?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#474?email_source=notifications&email_token=AAKMEY7B7J2XZIWCDYYOPETQK6MQBA5CNFSM4IZDPU5KYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4HM4S5UQ>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAKMEY25NKXYYHIP2DJ4D2LQK6MQBANCNFSM4IZDPU5A>
.
--
Shoumik
|
Great to hear that! On a related subject, are there any plans to use PyO3 or something similar for the Python wrapper to avoid manually setting |
I'd love to see Python3 support. Happy to give it a try if you want help testing. |
That would great! Expect a PR in the coming days here. @rth yes, we're eliminating the environment variables required to build it in this patch. |
Could we get an update on this? I still see all the docs use python3 atm. I would be happy to update the docs once this issue is resolved. |
Thanks for this library!
Just a reminder that most major scientific Python packages have dropped Python 2 support now, so only supporting Python 2 is quite problematic.
Related to #110
There was a WIP attempt in #132 that didn't receive much interest.
Is the Python 3 migration something you expect to happen? Any help needed there?
The text was updated successfully, but these errors were encountered: