opened
TomAugspurger
username_0
* [x] Used a fork of the feedstock to propose changes
* [x] Reset the build number to `0` (if the version changed)
* [x] [Re-rendered]( https://conda-forge.org/docs/conda_smithy.html#how-to-re-render ) with the latest `conda-smithy` (Use the phrase <code>@<space/>conda-forge-admin, please rerender</code> in a comment in this PR for automated rerendering)
* [x] Ensured the license file is being packaged.


@ocefpaf, when I re-rendered this locally, I got a warning

```
No numpy version specified in conda_build_config.yaml.  Falling back to default numpy value of 1.11
```

This is the first version of pandas requiring NumPy >=1.12. I set that in the `host` section of our recipe. Does that mean the warning can be ignored?
Rls 0.24.0rc1
issue
created
TomAugspurger
username_0
The previous commit pulled in NumPy 1.15.4, which we didn't want. With 
https://github.com/conda-forge/pandas-feedstock/pull/55/commits/d9e6c26279ce0dbf2b2e16e425178a3d7ecb7264 we'll hopefully build against the correct numpy for each platform.
comment
created
TomAugspurger
username_0
Great, NumPy 1.12 was used in the 2.7 build at https://circleci.com/gh/conda-forge/pandas-feedstock/237?utm_campaign=vcs-integration-link&utm_medium=referral&utm_source=github-build-link.

We'll need to do this same pinning for the final release.
comment