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 recipe for tinyarray #1444

Merged
merged 32 commits into from
Oct 27, 2016
Merged

Add recipe for tinyarray #1444

merged 32 commits into from
Oct 27, 2016

Conversation

basnijholt
Copy link
Contributor

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

@basnijholt basnijholt mentioned this pull request Aug 31, 2016
4 tasks
- toolchain
run:
- python
- nose
Copy link
Member

Choose a reason for hiding this comment

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

We need nose at build and run?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

You are right, it only needs it for building.

@patricksnape
Copy link
Contributor

It looks like this should build on Windows, the project is just using some Python functionality that doesn't exist on Windows in the setup.py (namely os.path.samefile). It looks like this is a custom method for getting the version from git - have you thought about using versioneer instead?

@patricksnape
Copy link
Contributor

Add the <algorithm> header to get std::max

@basnijholt
Copy link
Contributor Author

basnijholt commented Sep 3, 2016

I'm not really at home with C, so could you maybe help me by giving me the line I can copy paste into one of these files?

Edit: that was actually really easy...

@basnijholt
Copy link
Contributor Author

basnijholt commented Sep 3, 2016

Can someone help me on how I can run this Python file as test in meta.yaml?

The file is in MANIFEST.in, but I don't know where it is coppied.

For running that test file (test_tinyarray.py), nose is needed, does that make it a runtime dependency?

build:
- python
- setuptools
- nose
Copy link
Contributor

Choose a reason for hiding this comment

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

This isn't needed for building.

@conda-forge-linter
Copy link

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 (recipes/tinyarray) and found some lint.

Here's what I've got...

For recipes/tinyarray:

  • Failed to even lint the recipe (might be a conda-smithy bug) 😢

source_files:
- test_tinyarray.py
commands:
- $PYTHON test_tinyarray.py # [unix]
Copy link
Contributor

Choose a reason for hiding this comment

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

OK apparently Jinja doesn't like that, so just merge those two lines into a single one python test_tinyarray.py - sorry!

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

@basnijholt
Copy link
Contributor Author

Why does this Error: in section 'test': unknown key 'source_files' happen?

Outdated conda-build?

@msarahan
Copy link
Member

msarahan commented Sep 3, 2016

source_files was added in 2.0. It will not work with earlier conda-build
versions.

On Sat, Sep 3, 2016 at 10:43 AM Bas Nijholt [email protected]
wrote:

Why does this Error: in section 'test': unknown key 'source_files' happen?

Outdated conda-build?


You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#1444 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AACV-RQV1reXBCS5cYHMzwq2uuqxiNdoks5qmZW3gaJpZM4JxekI
.

@basnijholt
Copy link
Contributor Author

How can I use 2.0?

@patricksnape
Copy link
Contributor

patricksnape commented Sep 3, 2016

You can't until we fix a conda-build-setup bug.

@basnijholt
Copy link
Contributor Author

Let me comment out the tests untill then.

@patricksnape
Copy link
Contributor

The setup.py requires nose for setup but I don't think it should.

@patricksnape
Copy link
Contributor

Well, that's not true, if you want to use setup.py test - re-add nose to the build requirements if you don't want to change the setup.py - apologies!

@basnijholt
Copy link
Contributor Author

basnijholt commented Sep 3, 2016

I opened a pull request to fix it (shamelessly copied this).


source:
fn: v{{ version }}.tar.gz
url: https://gitlab.kwant-project.org/basnijholt/tinyarray/repository/archive.tar.gz?ref=v{{ version }}
Copy link
Contributor

Choose a reason for hiding this comment

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

So is this a tag or a branch? Is this the main repository?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

This is not the main repository, I've opened a pull request.

@basnijholt basnijholt mentioned this pull request Oct 10, 2016
5 tasks
Copy link
Member

@dopplershift dopplershift left a comment

Choose a reason for hiding this comment

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

This seems ready to go now.

@ocefpaf ocefpaf merged commit 8562e87 into conda-forge:master Oct 27, 2016
@basnijholt basnijholt deleted the tinyarray branch October 27, 2016 10:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging this pull request may close these issues.

7 participants