Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.maint.python > #11144
| From | Piotr Ożarowski <piotr@debian.org> |
|---|---|
| Newsgroups | linux.debian.maint.python |
| Subject | Re: packaging django-rest-framework-filters |
| Date | 2018-11-29 14:10 +0100 |
| Message-ID | <wZueS-2sE-17@gated-at.bofh.it> (permalink) |
| References | <wWPpv-7HD-3@gated-at.bofh.it> <wZs3o-VY-19@gated-at.bofh.it> <wZsZr-1wt-7@gated-at.bofh.it> <wZtC9-1ZB-3@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
[Scott Kitterman, 2018-11-29]
> dh-python already doesn't use upstream version requirements when automatically
> extracting dependencies, so you have to check those yourself regardless of how
> you do it. This design decision was based on generally poor experiences with
> the accuracy of upstream version descriptions (using exact version
> requirements is very common in the upstream Python community and that
> generally isn't supportable in Debian).
actually dh_python{2,3} extracts it, but only if package maintainer of
given module claims it is sane (via PEP386 tag in pydist file)
f.e. I consider Mako's versioning sane, so I added PEP386 tag to pydist
file in src:mako and now all packages that have "Mako>=1.0.3" in setup.py's
install_requires AKA requires.txt (do not confuse with requirements.txt)
will get the dependency.
Another way to get versioned dependency is to add version restriction in
Build-Depends (but that has to be updated each time upstream changes it,
it needs to be done for build tests anyway). This is only a bit better
than hardcoding it in Depends, though.
Note that it doesn't cover the "I tested it with latest Mako so lets
require latest one in install_requires" case, so I'm not promoting
PEP386 that much (IMO package maintainers have to translate minimum
required versions into proper Build-Depends dependencies by hand for
now)
--
GPG: 1D2F A898 58DA AF62 1786 2DF7 AEF6 F1A2 A745 7645
Back to linux.debian.maint.python | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
packaging django-rest-framework-filters Wookey <wookey@wookware.org> - 2018-11-22 06:10 +0100
Re: packaging django-rest-framework-filters Thomas Goirand <zigo@debian.org> - 2018-11-22 09:00 +0100
Re: packaging django-rest-framework-filters Wookey <wookey@wookware.org> - 2018-11-22 18:10 +0100
Re: packaging django-rest-framework-filters Piotr Ożarowski <piotr@debian.org> - 2018-11-22 22:30 +0100
Re: packaging django-rest-framework-filters Wookey <wookey@wookware.org> - 2018-11-26 05:10 +0100
Re: packaging django-rest-framework-filters Neil Williams <codehelp@debian.org> - 2018-11-28 10:00 +0100
Re: packaging django-rest-framework-filters Wookey <wookey@wookware.org> - 2018-11-28 15:40 +0100
Re: packaging django-rest-framework-filters Neil Williams <codehelp@debian.org> - 2018-11-28 18:00 +0100
Re: packaging django-rest-framework-filters Thomas Goirand <zigo@debian.org> - 2018-11-29 11:50 +0100
Re: packaging django-rest-framework-filters Neil Williams <codehelp@debian.org> - 2018-11-29 12:50 +0100
Re: packaging django-rest-framework-filters Scott Kitterman <debian@kitterman.com> - 2018-11-29 13:30 +0100
Re: packaging django-rest-framework-filters Piotr Ożarowski <piotr@debian.org> - 2018-11-29 14:10 +0100
Re: packaging django-rest-framework-filters Wookey <wookey@wookware.org> - 2018-12-08 05:00 +0100
csiph-web