On 28. 08. 20 20:31, Ankur Sinha wrote:
Hiya,
Is anyone working with python packages that use versioneer[1]? My
primary issue here is that upstream does not include tests in the pypi
tars, but because they use versioneer and it does all sorts of "magic":
- it is non trivial to figure out what untagged commit on Github matches
the latest pypi tar release
- even if one does manage to locate the commit, if we use the GitHub
archives, versioneer cannot get the version information from them:
https://github.com/warner/python-versioneer/issues/140#issuecomment-292746426
Does any one have any ideas here? I've requested upstream to include
tests in the pypi tars[2], but a way of forcing versioneer to provide the
correct version would be really nice.
[1] https://github.com/warner/python-versioneer
[2] https://github.com/BlueBrain/eFEL/issues/181
I remember it was but it was extremely hard to use anything but the sdist when
hacking on nb2plots. See:
https://src.fedoraproject.org/rpms/python-nb2plots/pull-request/2
Overall, versioneer behaves very badly when you try to bend it for RPM
packaging. Also, it appears upstream dead and this particular issue is not
getting anywhere:
https://github.com/warner/python-versioneer/issues/199
I'd ask upstream if they could consider using setuptools_scm instead.
--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
