-
Notifications
You must be signed in to change notification settings - Fork 19
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
Conda forge gdal issue #78
Comments
Something to do with cache. Hard to pin down, but its solved, hopefully save some time for someone else. I was only 1 minor version off up conda latest, but who knows.
Success. |
Thanks Ben! I may have time to look at this next month. Glad it is resolved all the same. The conda-forge stuff has been a very steep learning curve. |
Just as a heads up, I also needed to downgrade the numpy version to get
laspy to work.
```
(test) MacBook-Pro:NEON_crown_maps ben$ conda install numpy==1.16.4
Collecting package metadata (current_repodata.json): done
Solving environment: done
## Package Plan ##
environment location: /Users/ben/miniconda3/envs/test
added / updated specs:
- numpy==1.16.4
The following packages will be downloaded:
package | build
---------------------------|-----------------
numpy-1.16.4 | py37h6b0580a_0 4.1 MB
conda-forge
------------------------------------------------------------
Total: 4.1 MB
The following packages will be DOWNGRADED:
numpy 1.18.1-py37hde6bac1_0 -->
1.16.4-py37h6b0580a_0
Proceed ([y]/n)? y
Downloading and Extracting Packages
numpy-1.16.4 | 4.1 MB |
#################################################################### | 100%
Preparing transaction: done
Verifying transaction: done
Executing transaction: done
```
seems to be a known thing.
laspy/laspy#112
You might want to set a numpy== in the setup.py or conda yml.
…On Thu, Feb 6, 2020 at 3:58 PM Bryce Frank ***@***.***> wrote:
Thanks Ben!
I may have time to look at this next month. Glad it is resolved all the
same. The conda-forge stuff has been a very steep learning curve.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
<#78?email_source=notifications&email_token=AAJHBLEWJ6V3BIJMITZMIJLRBSPY7A5CNFSM4KRFLV42YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOELBHNGI#issuecomment-583169689>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAJHBLGWOI5BF6BXQBLTMZLRBSPY7ANCNFSM4KRFLV4Q>
.
--
Ben Weinstein, Ph.D.
Postdoctoral Fellow
University of Florida
http://benweinstein.weebly.com/
|
Going to re-open, I will take a closer look in the coming weeks |
hi @bw4sz et al 👋 👋 👋 👋 !! fingers crossed ...gdal has been behaving nicely for me lately and i have been using rasterio and updating environments without any issue. if for some reason i notice any other bugs however i will let you guys know because i haven't done a bit envt update in maybe a week or so? I hope this can be resolved!! i know gdal installs w python can be super tricky!! |
Confirmed that I had to downgrade to numpy 1.16.4 from numpy 1.18 on a second machine. This time a linux HPC machine. |
* Fix build on windows * Switch to conda build * Remove cuda dependencies * Set default actions shell to bash * Fix conda install on windows in GH actions test * Set bash as default shell * Test python 3.8 and 3.9 * Downgrade numpy See brycefrank/pyfor#78 * Tidy up action workflow * Fix install
Hello, I think I am experiencing a similar issue with Laspy v2.4.1
I get this error:
|
Hey Bryce. I'm debugging a pyfor install issue. I'll document here in case it happens to others. gdal and rasterio are failing on your conda forge build, but not only rasterio alone. Here is what I have so far.
Rasterio builds fine on its own. OSX.
Rasterio imports fine.
But within pyfor conda build it emerges.
There was an earlier issue that seems to be resolved for this same issue. @lwasser (hi! go earth lab/NEON) any recent problems? conda-forge/rasterio-feedstock#118
My interpretation is something about the pyfor conda forge build is conflicting with gdal and rasterio. All ideas welcome.
The text was updated successfully, but these errors were encountered: