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

spacy/attrs.pxd missing #7

Closed
jnothman opened this issue Jan 26, 2015 · 6 comments
Closed

spacy/attrs.pxd missing #7

jnothman opened this issue Jan 26, 2015 · 6 comments

Comments

@jnothman
Copy link
Contributor

Hey- compile (in fact, Cython translation) is failing due to uncommitted file (that should have been in the repo for 9 days). I think since this is now being advertised, you should probably move to off-site CI and tagged releases...

@jnothman
Copy link
Contributor Author

(Oh, and best of luck for the project!)

@honnibal
Copy link
Member

Hey

Argh, thanks. I'm using Travis, but I'm testing installation via pip. The attrs.pxd file ends up in the sdist, because it's in the package data.

I need to CI both installation from git clone and installation via pip. I'll figure that out.

@jnothman
Copy link
Contributor Author

Yes, always sdist from a fresh clone

@jnothman
Copy link
Contributor Author

You need a CI that tests master, and all pull requests, ideally (although I'm not sure what scale of contribution you expect/intend on this licensing model). It's pretty standard integration on github.

@honnibal
Copy link
Member

The problem is that the sdist relies on an intermediate state not in the repo --- the Cython-generated .cpp files. I have the CI set up to test the sdist because it's actually not so simple to build the .cpp files in a way that ensures the sdist doesn't depend on some side-effect of the Cythonizing.

Anyway. I'll find a way to fix this and ensure that both the installation from pip and the compilation from master are clean.

@lock
Copy link

lock bot commented May 9, 2018

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked as resolved and limited conversation to collaborators May 9, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants