-
-
Notifications
You must be signed in to change notification settings - Fork 5.1k
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
Created wrf-python recipe. #2229
Conversation
Hi! This is the friendly automated conda-forge-linting service. I just wanted to let you know that I linted all conda-recipes in your PR ( |
Is there anything else I need to do to convert this to a feedstock? Is this all automated from here? I have a talk at AMS on Monday, and was hoping to get a conda-forge package available for people that want to try it out. This package is related to NCL, PyNIO, and PyNGL. Thanks! |
Merge and wait 😄
Yep.
I am merging this now and hopefully the CIs will process this in time. I have a few minor comments that we can address later in the feedstock. Good luck with your talk! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the package. I no longer work with WRF
but I am curious to try it out!
|
||
about: | ||
home: https://github.com/NCAR/wrf-python | ||
license: "NCL Source Code" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please add a license_file
here. They are specially important for custom license like this one.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No problem. I'll add the license file to the recipe directory and follow the instructions in the docs.
- gcc # [unix] | ||
- libgcc # [unix] | ||
- xarray | ||
- vc 9 # [win and py27] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You don't need vc
s. Because this is depends on python at both build
and run
the right vc
will be always activated.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think I added this when I was trying to build against Python 3.5 on Windows and not having much luck. I'll remove it.
- wrapt | ||
- m2w64-toolchain # [win] | ||
- gcc # [unix] | ||
- libgcc # [unix] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If you need Fortran try the libgfortran
instead of libgcc
. (On Linux you may still need the libgcc
though if you need libquadmath
.)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I wasn't sure about this one. I think libgfortran is for OSX only, and libgcc is supposed to have the fortran symbols in them, and then one day that stopped working, so I just pulled the whole gcc in as well. I'll play around with it some more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is quite a mess in conda-forge, but here is the gist of it:
- if you need Fortran and
libquadmath
you needlibgcc
on Linux andlibgfortran
on OS X - if you only need Fortran you are OK with
libgfortran
on both - if you need
libgomp
you needlibgcc
on both, but then your package may be inconsistent on OS X because there people are usingclang
instead ofgcc
.
- wrapt | ||
- m2w64-toolchain # [win] | ||
- gcc # [unix] | ||
- libgcc # [unix] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You don't need libgcc
here because gcc
from above installs it for you. libgcc
is a run
time dependency only.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Will fix on feedstock.
|
||
requirements: | ||
build: | ||
- pip |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You probably need setuptools
, no?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Correct. I originally used pip, but during the try/fail cycle, I changed to setuptools. Will update the feedstock.
- pip | ||
- numpy x.x | ||
- wrapt | ||
- m2w64-toolchain # [win] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not sure if you need everything from m2w64-toolchain
to get Fortran on Windows. @mingwandroid probably know better.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Google searching led me to that solution.
Also, I can't build with Python 3.5. I think the mingw compiler now works with Python 3.5, but numpy distutils (and python distutils) needs patching. It looks like this is being addressed in numpy 1.13.
build: | ||
number: 1 | ||
detect_binary_files_with_prefix: true | ||
skip: True # [win32 or np>=112 or (win and py>=35)] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I usually have success building Fortran extensions on win32
. Just curious why you skipped it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Win32 didn't work for some reason. I'm not sure if it's the m2w64-toolchain, numpy's distutils, or me supplying the wrong compiler argument. It failed with a lot of missing python symbols, which should have been in libpython, so I don't think it got linked in correctly. Since I'm a little pressed for time, I decided to skip it, and will try to figure it out after AMS.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not sure why ATM, but something about this selector is causing problems in feedstock conversion. May require some investigation.
xref: https://travis-ci.org/conda-forge/staged-recipes/builds/193381312#L319-L328
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Raised this issue ( #2259 ).
No description provided.