Installation in Anaconda v5

[louiswicker]

Guys,

I am installing SHARPpy on a SuSE Linux distribution on an intel system at NSSL. I had to create a new conda environment to satisfy the pyside requirement (downgrade to qt=4.8), and so I did, cloned, and now when I run "python setup.py install" I get:

(sharppy) sh-4.3$ python setup.py install Traceback (most recent call last): File "setup.py", line 2, in from setuptools import setup, find_packages File "/scratch/software/Odin/python/anaconda2/envs/sharppy/lib/python2.7/site-packages/setuptools/init.py", line 13, in from setuptools.extension import Extension File "/scratch/software/Odin/python/anaconda2/envs/sharppy/lib/python2.7/site-packages/setuptools/extension.py", line 29, in _Extension = get_unpatched(distutils.core.Extension) File "/scratch/software/Odin/python/anaconda2/envs/sharppy/lib/python2.7/site-packages/setuptools/monkey.py", line 44, in get_unpatched return lookup(item) File "/scratch/software/Odin/python/anaconda2/envs/sharppy/lib/python2.7/site-packages/setuptools/monkey.py", line 55, in get_unpatched_class for cls in _get_mro(cls) File "/scratch/software/Odin/python/anaconda2/envs/sharppy/lib/python2.7/site-packages/setuptools/monkey.py", line 33, in _get_mro if platform.python_implementation() == "Jython": File "/scratch/software/Odin/python/anaconda2/envs/sharppy/lib/python2.7/platform.py", line 1460, in python_implementation return _sys_version()[0] File "/scratch/software/Odin/python/anaconda2/envs/sharppy/lib/python2.7/platform.py", line 1422, in _sys_version repr(sys_version)) ValueError: failed to parse CPython sys.version: '2.7.14 |Anaconda, Inc.| (default, Oct 16 2017, 17:29:19) \n[GCC 7.2.0]'

which looks like it does not like the v14 of 2.7 python. Thoughts? Suggestions?

[wblumberg]

Hey Lou, I haven't ever seen that before. Do you guys need to launch the GUI? If you don't, pyside is not needed. I also had some issues with installing in a conda environment the other day, but it wasn't this. The numpy installation wouldn't stick and many of the numpy tricks SHARPpy uses started throwing errors. Have you tried using v13 of 2.7 Python to see if that fixes the issue? It looks like this is possibly an issue with version 14 of platform.py included in python 2.7 not playing nicely with the anaconda version string. I'm still using version 12.

[louiswicker]

Greg,

I created a conda env with python 2.7.12, and things worked. So it might simply be a problem with sys check on the python version. I would have had to downgrade anyway, as qt=5.x now, which is incompatible for pyside=1.2.4

Lou

On Nov 7, 2017, at 11:32 AM, Greg Blumberg notifications@github.com wrote:

Hey Lou, I haven't ever seen that before. Do you guys need to launch the GUI? I also had some issues with installing in a conda environment the other day, but it wasn't this. The numpy installation wouldn't stick and many of the numpy tricks SHARPpy uses started throwing errors. Have you tried using v13 of 2.7 Python to see if that fixes the issue? It looks like this is possibly an issue with version 14 of platform.py included in python 2.7 not playing nicely with the anaconda version string. I'm still using version 12.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/sharppy/SHARPpy/issues/129#issuecomment-342559989, or mute the thread https://github.com/notifications/unsubscribe-auth/AAdFPnOe6fZquePbDBMzpDnj66dYN3siks5s0JQUgaJpZM4QVH3n.

---

Dr. Louis J. Wicker	NSSL/FRDD Rm 3336	National Weather Center	120 David L. Boren Boulevard, Norman, OK 73072
E-mail: Louis.Wicker@noaa.gov
HTTP: www.nssl.noaa.gov/~lwicker
Phone: (405) 325-6340
Fax: (405) 325-2316
Tell me and I forget. Teach me and I remember.
Involve me and I learn.
- Benjamin Franklin

---

	"The contents of this message are mine personally and	do not reflect any position of the Government or NOAA."

---

[wblumberg]

Lou,

That's good to know that that change worked. As you found out, the current iteration of PySide doesn't work with Qt5, but a new package called PySide2 does. @tsupinie and I have been working on upgrading SHARPpy to work with both Python 3 and PySide 2. I'd like to release those changes soon, but the current development version of PySide 2 (which has just has been made available through conda-forge) is causing SHARPpy to seg fault upon exit of the GUI for some reason. If the seg fault gets fixed in future iterations, I'll push the changes to our development branch.

[wblumberg]

@louiswicker ...we've been working on Python 3 version that is on conda now (conda install -c sharppy sharppy). It's an alpha version of the Andover branch...you might be interested in it. Now that PySide2 is out, we'll be trying to switch over to that after we officially release Andover. Need to do some testing with PySide2.