Python 3 support #10
Comments
|
Any progress on Py3.x support. Xarray is using Pynio as a ingest for grib... I am nearly 100% 3.x now and don't want to go back. |
|
Hi Scott and Daniel,
We are currently working on Python 3 support for PyNIO as a high priority
task. The developer is currently optimistic that it won't take too long so
hopefully it will be available fairly soon.
-dave
…On Mon, Jun 26, 2017 at 9:23 AM, Scott ***@***.***> wrote:
Any progress on Py3.x support. Xarray is using Pynio as a ingest for
grib... I am nearly 100% 3.x now and don't want to go back.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#10 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AB7VbWwlwJPMJwnQhDZtEgpuUNpkV797ks5sH8zlgaJpZM4LXoMx>
.
|
|
I'm working on an ML project for NASA (related to @darothen 's mention of |
|
@david-ian-brown any late summer updates on this? I have an application using HRRR GRIB2 output which leans heavily on xarray; if I could skip the step of converting GRIB2 to NetCDF (which would be possible with PyNIO support for Python 3), it would greatly help. |
|
I'm also super excited to see But for anyone reading this thread: in the meantime, if you use anaconda, you can easily create a python 2.7 virtual environment. This link has some great info. Create the environment with This is useful for any other packages that haven't yet been ported to python 3. |
|
@lukelbd that's true - but the scientific Python community is quickly moving away from Python 2, and there is little reason to maintain two fully functioning development environments for daily work. Virtual environments aren't a solution here in many cases. For instance, I'm building a workflow to ingest/parse GRIB2 output via xarray for work, and our entire stack is Python 3; it's hugely disruptive to maintain a separate Python stack on all our cloud services just to read those files into our system. |
|
@darothen you're absolutely right; just wanted to share a band-aid solution (viable for not-too-intensive workflows) until the python 3 update arrives. Though it looks like that will be imminent, so maybe it was not necessary. |
|
Unfortunately, the PyNIO port is taking a little longer than I expected, so I wouldn't say that release is imminent. It's currently in the debug stage, soon approaching testing. |
|
Thanks for hte update @bladwig1 . Is there anything the community to do at this stage to help out? |
|
PyNIO for Python 3.x is now merged in to the 'develop' branch on GitHub. However, an official release on conda-forge won't take place until a large amount of bug fixes related to compound data types, HDF5, etc are included. That being said, you should be able to pull down PyNIO from GitHub and start trying it out with Python 3.x. |
|
There is now a "dev" snapshot build on conda (ncar channel), which you can get by doing: conda create -n (your_env_name) -c ncar -c conda-forge pynio=dev python=3 If you notice any issues, please create a new GitHub issue. Thanks! |
|
Hey all - I know this thread is technically closed, but there's an issue with this old protocol. Somewhere along the line, a dependency issue was introduced. If you install a clean Python 3 environment with just xarray, a la: $ conda create -n test_nio -c conda-forge python=3.6 xarraythen activate it and attempt to install pynio as referenced above: $ conda install -c ncar pynio=devyou'll run into an issue with libnetcdf versions, where it requests a downgrade: Somewhere along the line, Any thoughts and/or solutions? This is new behavior; last time I helped someone get set-up with pynio/Python 3 back in January we did not run into this problem. |
|
Yeah add me to the list of people this no longer works for.. |
|
The issue here is a mismatch between the $ conda install --channel conda-forge/label/dev pyniothis would be in sync with the other dependencies we have in |
|
I can confirm that @ocefpaf's solution has worked just fine, and fixes the dependency issues. |
|
Thanks to @khallock who promptly created the dev version on PS: he also created a conda install --channel conda-forge/label/dev ncl🎉 |
|
Thanks all!
…-sent from a mobile device-
On Mar 18, 2018, at 1:57 PM, Filipe ***@***.***> wrote:
Thanks to @khallock who promptly created the dev version on conda-forge.
PS: he also created a ncl dev package too, install it with
conda install --channel conda-forge/label/dev ncl
🎉
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
|
FWIW, there may be a new issue - the resolved method isn't working, and is forcing a downgrade to Python 2.7. I think I've traced this down to an older version of cyordereddict which is pinned to Python 2.7, and is a dependency of xarray. |
|
@darothen what happens if you specify the python version too? Like conda create --name TEST --channel conda-forge/label/dev python=3.6 xarray pynioThe conda solver tries to wiggle its way out of complex dependencies by downgrading package version and build number, sometimes it even breaks channel preference! So the more you specify in the install command the better. |
|
@ocefpaf No dice, unfortunately:
|
|
Works for me, do you have other channel in your |
|
Oddly, no. I spun up a fresh VM, grabbed the latest |
|
Can you post the contents of your |
|
My |
|
Probably b/c the defaults added Note that, according to the docs, the |
In support of upstream Python 3 compatibility (NCAR/PyReshaper#26).
The text was updated successfully, but these errors were encountered: