Skip to content
This repository has been archived by the owner on Oct 13, 2020. It is now read-only.

NO MRG: MNT: Re-render the feedstock #3

Conversation

conda-forge-admin
Copy link
Contributor

@conda-forge-admin conda-forge-admin commented Aug 26, 2016

Please don't merge. This re-rendering has problems.

Hi! This is the friendly conda-forge-admin automated user.

I've re-rendered this feedstock with the latest version of conda-smithy (1.1.2) and noticed some changes.
If the changes look good, then please go ahead and merge this PR.
If you have any questions about the changes though, please feel free to ping the 'conda-forge/core' team (using the @ notation in a comment).

Remember, for any changes to the recipe you would normally need to increment the version or the build number of the package.
Since this is an infrastructural change, we don't actually need/want a new version to be uploaded to anaconda.org/conda-forge, so the version and build/number are left unchanged and the CI has been skipped.

Thanks!

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

@pelson
Copy link
Member

pelson commented Aug 26, 2016

@jakirkham - not good news on this one.

@jakirkham jakirkham changed the title MNT: Re-render the feedstock NO MRG: MNT: Re-render the feedstock Aug 26, 2016
@jakirkham
Copy link
Member

Seems that it has something to do with the enum34 selector in build. It can't just be py<34 and has to be something like py2k or (py3k and py<34). Alterntively, if enum34 is dropped from the build requirements, then the problem goes away too (note the selector remains the same in install). All of this is a bit odd, but I'm not sure what the cause is.

@jakirkham jakirkham closed this in #5 Aug 27, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants