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

Add bcolz #2322

Merged
merged 8 commits into from
Feb 8, 2017
Merged

Add bcolz #2322

merged 8 commits into from
Feb 8, 2017

Conversation

alimanfoo
Copy link
Contributor

Here's a recipe for bcolz.

@alimanfoo
Copy link
Contributor Author

@FrancescAlted I've added you as a maintainer. Please could add a comment to confirm this is OK.

@alimanfoo
Copy link
Contributor Author

@CarstVaartjes if you'd like to be added as a maintainer, let me know, happy to add you.

@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/bcolz) and found it was in an excellent condition.

@FrancescAlted
Copy link
Contributor

Yes, I am ok with being a maintainer. Thanks!

@CarstVaartjes
Copy link

For me it's not necessary (up to Francesc really), but would love to help where I can!

@alimanfoo
Copy link
Contributor Author

Currently builds for PY27 are failing because of Blosc/bcolz#322. We need a bcolz 1.1.1 release with the fix for that issue.

@FrancescAlted
Copy link
Contributor

bcolz 1.1.1 is out. Could you give it a try?

@alimanfoo
Copy link
Contributor Author

alimanfoo commented Feb 1, 2017 via email

@alimanfoo
Copy link
Contributor Author

@FrancescAlted could you release bcolz 1.1.1 on PyPI?

@FrancescAlted
Copy link
Contributor

Ooops. Uploaded the version in PyPI!

@alimanfoo
Copy link
Contributor Author

PY36 is failing on circle, error:

conda.exceptions.UnsatisfiableError: The following specifications were found to be in conflict:
  - numpy 1.9* -> python 2.6*|2.7*|3.3*|3.4*|3.5*
  - python 3.6*

Have no idea why it's trying to install numpy 1.9, the builds for PY27 and PY35 both install numpy 1.11 and build fine. Will see what happens on appveyor and travis...

@alimanfoo
Copy link
Contributor Author

Maybe forgot to update my fork of staged-recipes from upstream. Have rebased on upstream/master, see if that fixes the PY36 builds.

@alimanfoo
Copy link
Contributor Author

@conda-forge/core could you please help, builds for PY27 and PY35 are fine but PY36 builds are failing with this message:

conda.exceptions.UnsatisfiableError: The following specifications were found to be in conflict:
  - numpy 1.9* -> python 2.6*|2.7*|3.3*|3.4*|3.5*
  - python 3.6*

It looks like for the PY36 build the CONDA_NPY=19 variable is getting picked up, although it is ignored in other builds.

@patricksnape
Copy link
Contributor

patricksnape commented Feb 1, 2017

If you build against numpy you should have numpy x.x rather than just numpy

@alimanfoo
Copy link
Contributor Author

Thanks @patricksnape, forgot about numpy x.x.

Now builds failing because we don't have a pytables build for numpy 1.12. Have submitted a PR to the pytables feedstock: conda-forge/pytables-feedstock#10

@FrancescAlted
Copy link
Contributor

PyTables is an optional requisite, so why not leave it out?

@alimanfoo
Copy link
Contributor Author

alimanfoo commented Feb 2, 2017 via email

@jakirkham
Copy link
Member

As for pytables, it should be a simple matter of re-rendering that feedstock, which appears to already have been done in PR ( conda-forge/pytables-feedstock#9 ).

@alimanfoo
Copy link
Contributor Author

Thanks @jakirkham, the pytables builds are all there now so bcolz is building fine with all dependencies. This is ready to go AFAIC.

- bcolz
commands:
- python -c"import bcolz; bcolz.test(heavy=True)"
- python -c"import bcolz; assert set(bcolz.blosc_compressor_list()) == set(['blosclz', 'lz4', 'lz4hc', 'snappy', 'zlib', 'zstd'])"
Copy link
Member

Choose a reason for hiding this comment

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

For this sort of stuff, it may be better to move it to run_test.py. Should make it easier to read and follow. Plus it just runs with python. So there is no need for the python -c "...".

@jakirkham
Copy link
Member

One minor comment. Otherwise LGTM.

@alimanfoo
Copy link
Contributor Author

alimanfoo commented Feb 8, 2017 via email

@jakirkham
Copy link
Member

Sure. Let's do it. 👍

@jakirkham jakirkham merged commit a227f4f into conda-forge:master Feb 8, 2017
@jakirkham
Copy link
Member

Also am working on a longer term fix to the Travis CI issues.

xref: conda-forge/conda-forge-build-setup-feedstock#52

@alimanfoo
Copy link
Contributor Author

alimanfoo commented Feb 8, 2017 via email

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.

6 participants