-
Notifications
You must be signed in to change notification settings - Fork 15
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.7 and 3.8 compatibility #128
Comments
I think the only thing that needs to change is that new packages need to be built. Basically, if you bump the build number in the You could probably install with Pip, provided that you installed all the dependencies of PyKED first and then just used pip to install PyKED. Or you could install from source. |
Yeah, I was about to say the same. I imagine/hope most dependencies support 3.7, but 3.8 is probably less likely at this point. |
Quick look at dependencies:
The problem might be Cerberus. Right now we only support up versions below 1.2, and v1.1 only supports up to Python 3.6. (It looks like for v1.2 and v1.3.1 now have noarch packages...). @bryanwweber do you recall why we limit Pint to <0.9? |
The upper limit on all the dependencies is basically best practice, to avoid breaking changes assuming they follow semver. Since Pint is still zero-ver, it seemed best to limit to the next point release. |
@nateharms if you have the bandwidth, it'd be great if you could check out PyKED's compatibility with newer versions of those dependencies—that will make it easier for us to support Python 3.7+. But, if cerberus is really limiting us here, then I guess we'll need to revisit the issues limiting us to v1.1 |
I don't mind looking into it, I'll let y'all know how things progress. |
Okay, from working with the Added:
Modified:
And when running
And then the tests (
NOTE: I modified the |
So, at least hypothetically, @kyleniemeyer (as the maintainer of the Cerberus conda-forge feedstock) could push a commit there that bumps the build number for 1.1 and sets it to a noarch package, then another commit to come back to the current version. I'm not sure if conda-forge would approve of that, but what they don't know? |
But honestly, you're probably better off with pip here. Just create a new environment, conda install everything except PyKED and Cerberus, then |
Update: I set up my environment according to @bryanwweber's suggestion and everything is working in order. It's a good workaround for now, but maybe a change that could be addressed in the future? Thanks again for y'all's help! |
Right, the key here is that we need to fix or remove the dependence on Cerberus. Feel free to jump in to that 😄 |
I'm mainly posting this issue for discussion and to highlight possible todos.
I was trying to install PyKED and PyTeCK in an environment that requires python 3.7+. I ended up spending a fair amount of time banging my head against the wall with Anaconda until I realized that PyKED (and PyTeCK subsequently) uses python 3.6. Given that Python 3.8 has been released, should there be an effort to convert/modify aspects of PyKED (and PyTeCK) to support 3.7 and 3.8? If so what changes need to be made?
The text was updated successfully, but these errors were encountered: