Path: csiph.com!news.mixmin.net!aioe.org!bofh.it!news.nic.it!robomod From: Wookey Newsgroups: linux.debian.maint.python Subject: Re: packaging django-rest-framework-filters Date: Wed, 28 Nov 2018 15:40:01 +0100 Message-ID: References: X-Mailbox-Line: From debian-python-request@lists.debian.org Wed Nov 28 14:38:34 2018 Old-Return-Path: X-Amavis-Spam-Status: No, score=-14.3 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, LDO_WHITELIST=-5, PGPSIGNATURE=-5, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham autolearn_force=no X-Policyd-Weight: using cached result; rate: -6.1 Mail-Followup-To: Neil Williams , debian-python@lists.debian.org MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="64ps6qihbdgpcfkf" Content-Disposition: inline Organization: Wookware User-Agent: NeoMutt/20170113 (1.7.2) X-Mailing-List: archive/latest/16582 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/20181128143820.xkdawzmo3nvy4wg2@mail.wookware.org Approved: robomod@news.nic.it Lines: 107 Sender: robomod@news.nic.it X-Original-Cc: debian-python@lists.debian.org X-Original-Date: Wed, 28 Nov 2018 14:38:20 +0000 X-Original-Message-ID: <20181128143820.xkdawzmo3nvy4wg2@mail.wookware.org> X-Original-References: <20181122050200.tcg7urpyqjd5rx7n@mail.wookware.org> <20181126040505.hzyhkmatjcmrglg4@mail.wookware.org> <20181128085853.65613f39@calvin.codehelp> Xref: csiph.com linux.debian.maint.python:11138 --64ps6qihbdgpcfkf Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2018-11-28 08:58 +0000, Neil Williams wrote: > On Mon, 26 Nov 2018 04:05:05 +0000 > Wookey wrote: >=20 > > On 2018-11-22 08:59 +0100, Thomas Goirand wrote: > > > On 11/22/18 6:02 AM, Wookey wrote: =20 > >=20 > > I guess djangorestframework-filters is > > clearer, and closer to upstream so people can find it. I'll go with > > that unless someone says the drf-* names are a better plan. > >=20 > > OK. I've made a new package (djangorestframework-filters), which > > seems OK. (actually I've made 2 (see below)) > >=20 > > I'm not a member of the modules team, so can't follow the instructions > > to make a salsa project under the python-team banner > > (https://wiki.debian.org/Python/GitPackaging) > >=20 > > I'll put it under wookey for now. > >=20 > > Also, the latest release is 0.10.0.post0, which says it's compatible > > with: > > * **Python**: 2.7 or 3.3+ > > * **Django**: 1.8, 1.9, 1.10, 1.11 > > * **DRF**: 3.5, 3.6 >=20 > djangorestframework lists "Breaking changes" in the release notes for > 3.8, so this looks like an incompatibility with what's already in > Debian. >=20 > https://github.com/encode/django-rest-framework/releases/tag/3.8.0 >=20 > It might be worth testing whether 0.10.0.post0 or another release of > django-rest-framework-filters between that and 1.0.0dev0 is actually > fine with djangorestframework 3.8 - at least at a unit test level. Milosz and I are doing just that. It would be great if you could check whether these packages work OK with lava or not as that's at least one datapoint: http://wookware.org/software/repo/pool/main/d/drf-extensions/python3-django= restframework-extensions_0.4.0-1_all.deb http://wookware.org/software/repo/pool/main/d/djangorestframework-filters/p= ython3-djangorestframework-filters_0.10.2.post0-1_all.deb > > However the version of DRF in testing is now 3.8, and python 3.6 so > > perhaps it's better to upload the upcoming v1.0.0.dev0: > > * **Python**: 3.4, 3.5, 3.6 > > * **Django**: 1.11, 2.0, 2.1b1 > > * **DRF**: 3.8 > > * **django-filter**: 2.0 > >=20 > > But the version of django-filter in debian is 1.1.0, so at first > > glance neither of these versions will work with the components > > available. > >=20 > > I'd normally upload the last released version, i.e. 0.10.2.post0, but > > I'm not sure how these interactions with versions of > > djangorestframework and django-filter work. Any advice or shall I work > > this out with upstreams? >=20 > django-filters has a new upstream 2.0 but a migration guide has been > published for that: >=20 > https://django-filter.readthedocs.io/en/master/guide/migration.html#migra= ting-to-2-0 Cheers for that link > So it's likely that at least some reverse dependencies would be broken > by django-filters version 2.0. As you say - if we have to go to django-filters 2.0, then things probably get complicated (too complicated for buster). Wookey --=20 Principal hats: Linaro, Debian, Wookware, ARM http://wookware.org/ --64ps6qihbdgpcfkf Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEER4nvI8Pe/wVWh5yq+4YyUahvnkcFAlv+qFcACgkQ+4YyUahv nkf4MhAAp7nrU+M74OQccFDMoDKY+LlcNbhejNyBIe9pjyN4WvxbiMdXiwrMlNBT UvOhEJnI8bIn0c5EGJ7NMLBfwS9HcePcfqVJCfl2EzUUjmpMyCfZtkptOjGLnU7t KlJ0/0gl522Em4MKWmLsa4Sk0qICvzp7zpkSfT98RuVXcmczSf7Q2eJyrfq5xz+m wv3wsHD/cDQGMW6wl9/KzhkMgj4uCdnOiLcTCIxtVpQv1DTQ/hBlRWLi6oWV9ZG/ 4emMrF/JEuiIlDDGPqsK7Z7SA5lRAqDYtlK0sywKRETP+gbC5Y4v+6YknkHbyITO QnNVLU3j1n7zBKC0jBzX98PAirbwHviba74juBLRPu/TrWssycw2u/rIH+3LWTcn HF+AkeJpFna9ocJnP9DLlGyLf+0+E+LuqT5/lV8e+1UrMRSHQbgoZDXmzGeIIFJg s4ftRk3p49jCA6oxDFBVKIoKd4QZytHx4gYLZSzjYRWV61n7XPsdbD839NHthRJK V0gB74Ixyu6yB62Ma9/9o6Bnm7JEqtuqwM02/2yNRGQi/iuqncCxl2a6AIJFm0b6 Z2R7a6o91jVP0FHbMtKGCP1TlaDKVEYmdV14jYg1Ds2M5stGNQQxY9JBo9gybA+2 BUujMra9h5vWq0X6dVKXp5mpmi91NGtIlDkF+4ujRwhkEp8FDcY= =iOHa -----END PGP SIGNATURE----- --64ps6qihbdgpcfkf--