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

Changed default policy for dirty repositories to 'report' #41

Merged
merged 5 commits into from Apr 23, 2018

Conversation

jlstevens
Copy link
Contributor

This is a friendlier default e.g for python setup.py develop.

@ceball
Copy link
Member

ceball commented Apr 22, 2018

I think report is the right default. (I also think strip shouldn't exist - or at least, I can't see why I'd want to use it.)

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 +...-dirty (or similar) in its name, so that pypi would reject it.

@jlstevens
Copy link
Contributor Author

I think that test should be replaced with one that checks the generated package name has +...-dirty (or similar) in its name, so that pypi would reject it.

Sounds sensible to me! I assume conda channels wouldn't reject such a version?

@ceball
Copy link
Member

ceball commented Apr 22, 2018

I assume conda channels wouldn't reject such a version?

I forgot to mention conda: conda packages can't have - in the version.

pypi would reject because of +.

So +...-dirty should be fine for both. I think...we'll see :)

@ceball
Copy link
Member

ceball commented Apr 22, 2018

Any reason this branch wasn't made from latest master?

@ceball
Copy link
Member

ceball commented Apr 22, 2018

Hope not, because I just rebased it...

@ceball
Copy link
Member

ceball commented Apr 22, 2018

If the tests pass, I'm done with this PR and it could be merged from my point of view.

@jbednar jbednar merged commit dfd0bec into master Apr 23, 2018
ceball added a commit to holoviz/param that referenced this pull request Apr 24, 2018
  * Allow develop_install to work (holoviz-dev/autover#41)

  * Failed to report 'dirty' for commit count of 0 (holoviz-dev/autover#44)
ceball added a commit to holoviz/param that referenced this pull request Apr 24, 2018
* Allow develop_install to work (holoviz-dev/autover#41)

* Failed to report 'dirty' for commit count of 0 (holoviz-dev/autover#44)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants