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
Changed default policy for dirty repositories to 'report' #41
Conversation
I think The tests have failed because the version.py files in pkg_bundle and PkgBundle haven't been updated (there's a test checking they're the same as in autover itself, since we can't use symlinks). After that, the tests should then fail again, because there's a test that an error is raised on attempting to package a dirty repo. I think that test should be replaced with one that checks the generated package name has |
Sounds sensible to me! I assume conda channels wouldn't reject such a version? |
I forgot to mention conda: conda packages can't have pypi would reject because of So |
Any reason this branch wasn't made from latest master? |
c5a4cd8
to
d7c28c2
Compare
Hope not, because I just rebased it... |
… be uploaded to pypi, and that conda won't build.
If the tests pass, I'm done with this PR and it could be merged from my point of view. |
* Allow develop_install to work (holoviz-dev/autover#41) * Failed to report 'dirty' for commit count of 0 (holoviz-dev/autover#44)
* Allow develop_install to work (holoviz-dev/autover#41) * Failed to report 'dirty' for commit count of 0 (holoviz-dev/autover#44)
This is a friendlier default e.g for
python setup.py develop
.