-
Notifications
You must be signed in to change notification settings - Fork 21
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
Environments.yml requires gssha - not available for Windows #8
Comments
I can only suggest disabling those dependencies for now. If these issues can't be addressed in the near future it might make sense to have separate environments for building the full documentation which includes GSSHA examples and one for users to try out the other content. |
@kcpevey Amanda Hines is working a Windows GSSHA conda package. Getting pangaea available for Python3/Windows so that GSSHApy will install is on us (ERDC). |
Actually, now that I think about it no she isn't. She's working on merging some GSSHA branches so we can start building GSSHA packages. Either way the Windows GSSHA package is on us. |
I just looked through the earthsim dependencies and it looks like the only current GSSHA-related dependency is gsshapy. I suspect the If that is true, then this issue boils down to updating Pangaea (https://anaconda.org/conda-forge/pangaea). |
Ok so this is a casualty of Alan Snow (@snowman2) moving on to greener pastures. He was the primary developer of gsshapy for a while and he added some dependencies to a couple of projects he created. Pangaea is one of his projects. We either need to update gsshapy to drop the pangaea dependency, update pangaea to be windows & python 3 compatible or investigate if pangaea is an optional dependency and update the conda-forge build recipe package to drop pangaea. All three options require one of us investigating, making the changes and then either doing a pull request on Alan's repos or asking him to make one of us a maintainer on those repos. |
Pangaea is already available for py3 for OSX and Linux. I don't know enough about cross-platform development, but could it be that Pangaea was simply not built for Windows? I did some testing on my Windows machine. First, I cloned the Pangaea repo and tried to Is that helpful? What else can I check? Should I just try to build the conda package? (Not sure how to do that...) |
I added Win64/Python3 packages for |
Just to be clear, the yml needs the following modifications:
Is all that correct? |
Actually which yml file are you looking at? This one already has the correct quest repo: https://github.com/pyviz/EarthSim/blob/master/environment.yml |
Thats the one I'm looking at. I knew quest moved, but stupidly didn't realize the yml was already updated. As for holoviews and geoviews, I thought @philippjfr told me to pull from I guess I also don't understand why holoviews and geoviews are imbedded in the pip command instead of pulling from conda? |
So the pip commands pull directly from the latest github branches. I think now holoviews and geoviews automatically build conda packages every night and put them in the |
That's not yet the case as there is still some churn around our packaging/release procedures, which should all be solved in the coming weeks. I don't remember when I originally gave that advice, currently the way to get the latest versions would be to install holoviews from That said I think for development purposes we will probably want to track master (using pip), and separately have semi-regular EarthSim/HoloViews/GeoViews dev releases which pin specific versions and guarantee a bit more stability. |
Ok. The only change I made to the yml was removing First, I'll say that I had multiple connection errors when it was getting At any rate, it did finally download and I got past the The beginning of a thousands of lines of error:
|
So I've had this issue on Windows and it is something to do with conda-forge and default channels packages overwriting some common files. I fixed it by change my conda settings to
I also had to first create a basic conda config file since I didn't have a user editable one in my path:
|
@dharhas I set it warn but I'm getting the same verification errors and now the ClobberErrors are ClobberWarnings. I noticed that the verification errors are focusing on pip. I've been getting warnings that my pip needs to be upgraded to 10.0.1, but my update is failing with an Attribute Error deep inside the script. I'm thinking the best approach would be to just get rid of pip and reinstall, but I'm not clear on how intrinsic that is to my python installation. If I delete it on my own, will I destroy my python installation? |
|
I did I decided to delete my pip and wheel directories. My
I'm starting to think that I'm going to have to delete python/anaconda altogether and start over from scratch.... |
That might be the simplest. Also unless you use the other stuff that comes with Anaconda, i.e. like the navigator GUI etc, I would just install miniconda. |
Ok. Will do... |
Whew. I completely removed python from my machine and reinstalled it. I removed gssha from the yml then used it to create a conda env. I still got I ran |
Just for the record... I think my issues had something to do with pip not playing nice with conda. Last week pip started warning me to update from 9.0.3 to 10.0.1. I went ahead and updated pip outside of conda (10.0 is not available via conda yet). That |
ok as a rule of thumb never mix conda with non conda stuff. Pip can be installed inside conda packages but using a system pip can cause issues as you saw. There are some breaking changes in pip 10 that are causing issues all over the python ecosystem which might be why conda is not upgrading pip yet. |
Lets leave this issue open until we have the windows gssha package available. |
I'm finally getting around to testing this more extensively.
|
I wonder if this is due to the new environment stacking feature in conda. Try |
the It appeared to have been a problem with my paths (Windows). I had my root conda directory (and the libraries, site-packages, etc) in BOTH my system path AND a PYTHONPATH environment variable. It was the SAME set of directories so I don't understand why that caused problems. I deleted everything out of PYTHONPATH and now my workflow notebooks are running smoothly. |
Yeah conda recommends not setting PYTHONPATH or PYTHONHOME -> https://conda.io/docs/user-guide/troubleshooting.html |
gssha 7.12 should now be available on all three platforms (OSX, Win, Linux) as a conda package in the erdc channel. I installed and checked that it ran and gave me usage instructions. I haven't tested by run any models, so please let me know if you hit issues. |
I came here to post that I just packaged the gssha 7.0 binary for win-64, and that it seems to work but will be testing it properly tomorrow in the EarthSim notebooks. But now I'll test yours instead :) |
I built on win10. Did not try win7
…On Tue, Apr 24, 2018, 4:35 PM Chris B ***@***.***> wrote:
On a windows 7 machine, I did conda install -c erdc gssha into a fresh
python 3.6 environment. It installed fine, but when I type gssha I get: The
program can't start because VCOMP90.DLL is missing from your computer. Try
reinstalling the program to fix this problem.
[image: gssha]
<https://user-images.githubusercontent.com/1929/39215449-c309728e-480f-11e8-9ac8-5ef754cfcb74.png>
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#8 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAiQlW4mDyMw9uheyxzEap1roth5XPtiks5tr5qhgaJpZM4SCXZc>
.
|
I'm stopping for today, but can test out anything new tomorrow (on win7 and win10). But if you don't get chance, it won't hold me up as I can use the package I made (and we can replace it later on with yours). |
Ok l think it is because I did not make openmp a runtime dependency. Can you install openmp from conda forge and see if that fixes it. I'll try and fix the packagre later. I'm out and about right now. |
Ok its something to do the vs runtime. The package I built is dependent on the vs2008_runtime but the vs2015_runtime is being installed. Working on a fix. |
When I installed, python was downgraded from 3.6 to 2.7:
But it runs :)
I can try to inspect the recipe later (presumably it's available?). But just guessing, if you depended on vc=9 at run time, I think that would tie it to python 2.7. |
Boo. So I can't get it to compile with VS2015. I think there is some C++ constructs that are not compatible... Its a pure C++ code with no python dependencies so I was hoping I could get away with vc9 Earlier version. I was accidentally setting the meta.yaml to vc14 but it was compiling with vc9 because it was in the path and it built a package that was usable as long as you installed vs2008_runtime into your conda environment. For now lets stick with your repackaged version, I don't have cycles to spare on this right now... |
Try again. I've uploaded a new build that is compiled with vc9 but only dependent on the vs2008_runtime. This allows me to install it in a python 3 environment. The following works for me now:
You should be getting build 26:
|
@dharhas It found the correct package and installed without errors. The gssha package (with correct version and build) is showing up in my conda list. I wrote a little test script that just imports gssha, but its failing to import.
|
@kcpevey you also need to install gsshapy.
|
@dharhas gsshapy is already installed I also ran My env is py 3.5 for earthsim, is that ok? |
OHHH I think I see what you're saying... You can't import I'll find the example notebooks to test. |
@dharhas |
I'll close this, although I've seen longer issues ;) If I have trouble with the example notebooks, I'll open a new issue. Meanwhile, @kcpevey, I have an unrelated question. Are you using the Anaconda Prompt on windows, or something else (e.g. git bash)? Or do you have bash/similar installed some other way (e.g. via conda, or as part of windows 10 maybe)? I noticed when you pasted your session, it looked like some kind of bash. |
@ceball I usually use gitBash since its generally my favorite. However, I'll say that when I use gitBash to add/remove packages from a conda env, it does the task successfully, but ends up breaking the path to my conda tools. So if I add a package to an env via Because of that, I've added the unix commands to the native Windows Command Prompt and occasionally I'll use that when I get annoyed with gitBash. All that to say, I'm fairly certain that all the above discussions were run with gitBash. |
The env cannot be set up on Windows as-is since the gssha package is only available for Linux and OSX (https://anaconda.org/gbrener/gssha).
There are other gssha-related Windows issues as well. Namely the fact that earthsim is on py3.5, requires gsshapy, and gsshapy requires pangaea which is not available for Windows py3.5. (https://github.com/ContinuumIO/EarthSim/issues/124)
The text was updated successfully, but these errors were encountered: