-
-
Notifications
You must be signed in to change notification settings - Fork 10
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
Cesc/update recipe #2
Cesc/update recipe #2
Conversation
Hi! This is the friendly automated conda-forge-linting service. I wanted to let you know that I linted all conda-recipes in your PR ( Here's what I've got... For recipe:
|
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 ( |
Just curious, is Windows out of the question for blosc? |
That's a good question for @msarahan . |
The failure on Travis CI is due to the feedstock needing an update. Please re-render with |
Thanks for the help, rerendering added missing appveyor file for windows |
@@ -1,39 +1,44 @@ | |||
{% set version = "1.3.2" %} | |||
{% set name = "blosc" %} |
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.
Why the name change? Shouldn't this still be python-blosc
? Note we do package blosc
also.
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.
When you install one wants to run it you run, import blosc
I thought this would be less confusing, but the repo is called python-blosc
. Changing the name back to python-blosc
e0f0754
recipe/meta.yaml
Outdated
run: | ||
- python | ||
- blosc |
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.
Why are we dropping blosc
as a dependency?
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 was doubting on this, I could not understand why do we need the package itself as a dependency?
1725c1a
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.
blosc
is refering to the c-blosc
lib, the recipe for that one is here: https://github.com/conda-forge/blosc-feedstock. This one python-blosc
is just the python wrapper. We decided on those names to have the same ones as the defaults
channel, here is the full discussion: conda-forge/staged-recipes#918
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.
So python-blosc
will build c-blosc
if its not found (in the setup.py) but if we add it as a dependency it will just link it to the c-blosc
that we build.
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 guess the question will arise how we build c-blosc
/blosc
on Windows.
@msarahan can you please advise us on this? 😄
recipe/meta.yaml
Outdated
- numpy | ||
|
||
test: | ||
imports: | ||
requires: | ||
- blosc |
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.
😕
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.
recipe/meta.yaml
Outdated
- blosc | ||
commands: | ||
- python -c "import blosc; blosc.test()" | ||
- mkdir empty | ||
- cd empty |
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.
Why is this needed?
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.
In my opinion we don't need it, I was just following the travis.ci file from the python-blosc project. so removing it
390e29d
recipe/meta.yaml
Outdated
|
||
about: | ||
home: https://github.com/Blosc/python-blosc | ||
license: Apache 2.0 | ||
license_file: LICENSES/PYTHON-BLOSC.txt |
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.
👍
recipe/meta.yaml
Outdated
- mkdir empty | ||
- cd empty | ||
- python -c 'import blosc; blosc.print_versions()' | ||
- python -c 'import blosc; blosc.test()' | ||
|
||
about: | ||
home: https://github.com/Blosc/python-blosc | ||
license: Apache 2.0 |
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.
We could also optionally add license_family: Apache
.
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 believe I still need some input for the license, apparently there are some plans to change it to bsd Blosc/python-blosc#121 (comment)
Adding it acbca92
Ah, yeah, if you change |
README.md
Outdated
@@ -1,5 +1,5 @@ | |||
About python-blosc |
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 guess that is is because of the rerendering of the feedstock? Maybe you need to rerender again.
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. After fixing the name we will need another re-render. Note can do conda smithy rerender --commit
to commit the changes. Also can tack on auto
to commit the re-rendering automatically without reviewing the changes.
+1 Great to see a maintainer come in for this one :D |
Could you please disable CircleCI on your fork @FrancescElies ? It seems to be building this PR on your fork instead of on this feedstock. |
Also please close and reopen this PR after you have done that. This will trigger CircleCI to correctly build on this PR. |
I deactivated Circle Ci, Travis and Appveyor from my profile |
By the way, thank you both for your help! |
Reopened to trigger CI services |
recipe/meta.yaml
Outdated
|
||
requirements: | ||
build: | ||
- python | ||
- setuptools | ||
- blosc |
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.
Shall I add this build requirements again?
The git history is a bit messy, once this PR is fine I could clean the history if you like.
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.
Yes, let's go ahead and do that.
Sure if you want to clean it up at the end that sounds like a good idea.
We have a c-blosc recipe internally, but I don't see packages, and I don't understand why. Internally, I think we decided to change the compiled library to c-blosc, because that matches the project name. |
Now I just remembered why I changed the name of the package, from |
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.
Naming is causing us some issues with the download. As it is called blosc
on PyPI, but we call it python-blosc
here, we need to make a few corrections.
recipe/meta.yaml
Outdated
|
||
package: | ||
name: python-blosc | ||
name: {{ name|lower }} |
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.
Maybe we should make this python-{{ name|lower }}
.
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.
sounds good to me
recipe/meta.yaml
Outdated
@@ -1,39 +1,44 @@ | |||
{% set version = "1.3.2" %} | |||
{% set name = "python-blosc" %} |
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.
Maybe we should change this to blosc
.
url: https://github.com/Blosc/python-blosc/archive/v{{ version }}.tar.gz | ||
sha256: 63d1cd1da14087fa69bffc513b25d59deb24f45c65e4406acafaaa6ec9bd7cf2 | ||
fn: {{ name }}-{{ version }}.tar.gz | ||
url: https://pypi.io/packages/source/{{ name[0] }}/{{ name }}/{{ name }}-{{ version }}.tar.gz |
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 then should work.
Seems our comments passed each other. My comments should address the download issue. |
e2c0ca4
to
59b4fbb
Compare
59b4fbb
to
6bdfb32
Compare
So I think this is mostly good now. The one issue is that we still don't have a
Not sure which will be best. |
6bdfb32
to
98e148d
Compare
I'm not sure, to me the cleanest sounds (1.), but maybe for the moment we could skip windows. I'm easy |
I actually have some questions |
|
|
Me too. 😄 Would love to get it to work on Windows at some point though. 😉 |
f83563f
to
7115989
Compare
It looks like something wen't wrong now, |
regtriggering CI services |
Recommend retriggering CI services again |
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 ( |
Retriggered (close-open PR). I see appveyor and travis running again but not circle ci |
an empty commit retriggered circle ci (I'll remove it afterwards) |
bed8d7d
to
403f841
Compare
removed empty commit, + rerendering, fingers crossed |
403f841
to
d0ab9d9
Compare
tests passed now |
bumps version, adds some fixes, a maintainer and a todo for the test section