Versioning fails when 'CI' is 'true' about quaternion HOT 8 CLOSED

In your .travis.yml file, I'm guessing you have a section with something like

install:
  - pip install numpy numpy-quaternion

Try changing that to

install:
  - pip install numpy
  - CI=false pip install numpy-quaternion

That sort of thing would work in bash by just changing the value of CI for that one command. Hopefully travis doesn't do so much "magic" that this is broken.

Unfortunately, auto_version is a little too dumb and used throughout too many of my projects to provide a more elegant solution. I'm afraid I don't really use pip myself, and I won't have a lot of time for this stuff any time soon (we're having twins!), so I'm sorry if this isn't the most robust or helpful solution, but I am open to suggestions that don't break my own process.

from quaternion.

Thanks for a very speedy response, at least. Actually in my .travis.yml file I have a pip install . which installs my own module and its dependencies from setup.py. I could no doubt break out the dependency separately as you suggest but as you note it is not super elegant, as it removes the automatic installation that pip otherwise provides.

From my point of view the obvious question is whether it is necessary to error out on CI if the git command fails. I guess that you put that in to make sure that it was working early on, but I don't see why that is a useful feature now. Not suggesting that it needs to be changed though, I can work around it as you suggest. I will close the issue for now.

from quaternion.

This is a legitimate problem, so I'll leave it open in case other people come looking for a way to solve it.

From my point of view the obvious question is whether it is necessary to error out on CI if the git command fails.

My answer is yes. The problem is that the CI process doesn't just test, but also uploads pip and conda packages, and those packages get their versions from this git information. Some times git does indeed fail, even now when things are generally working — usually due to subtle errors or changes in travis-ci. These particular version numbers fulfill a few requirements, including solving conda dependencies, and ensuring that data produced from my code (in which I include the version numbers of any packages I use) can be easily traced back to its origins down to the commit level. So I definitely don't want the packages going out if they can't get their version numbers. There's probably a better way to set the versions using git hooks, but it won't be easy for me to change at this point.

from quaternion.

This should be fixed since b732124, which simplified the version number so that it no longer uses auto_version (even though the submodule is still in the code...).

from quaternion.

Should this work now then?
pip install --no-cache-dir numpy numpy-quaternion because this still fails for me

from quaternion.

This is still an issue @moble

from quaternion.

@Achllle No, this is not still an issue; the issue you appear to be talking about is jvgomez's question, which is a different issue. This issue was about the CI stuff. See #99.

from quaternion.

Alright, sorry that I commented on this issue. Seems like it's the same as #99 in that case.

from quaternion.