Skip to content
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

Merged
merged 10 commits into from
Jan 19, 2017
Merged

Created wrf-python recipe. #2229

merged 10 commits into from
Jan 19, 2017

Conversation

bladwig1
Copy link

No description provided.

@conda-forge-linter
Copy link

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 (recipes/wrf-python) and found it was in an excellent condition.

@bladwig1
Copy link
Author

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!

@ocefpaf
Copy link
Member

ocefpaf commented Jan 19, 2017

Is there anything else I need to do to convert this to a feedstock?

Merge and wait 😄

Is this all automated from here?

Yep.

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!

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!

@ocefpaf ocefpaf merged commit 5139a0a into conda-forge:master Jan 19, 2017
Copy link
Member

@ocefpaf ocefpaf left a 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"
Copy link
Member

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.

Copy link
Author

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]
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You don't need vcs. Because this is depends on python at both build and runthe right vc will be always activated.

Copy link
Author

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]
Copy link
Member

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.)

Copy link
Author

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.

Copy link
Member

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 need libgcc on Linux and libgfortran on OS X
  • if you only need Fortran you are OK with libgfortran on both
  • if you need libgomp you need libgcc on both, but then your package may be inconsistent on OS X because there people are using clang instead of gcc.

- wrapt
- m2w64-toolchain # [win]
- gcc # [unix]
- libgcc # [unix]
Copy link
Member

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.

Copy link
Author

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
Copy link
Member

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?

Copy link
Author

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]
Copy link
Member

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.

Copy link
Author

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)]
Copy link
Member

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.

Copy link
Author

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.

Copy link
Member

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

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Raised this issue ( #2259 ).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

4 participants