Re: RFS: python-jsonref 0.1

2016-12-31 Thread Mattia Rizzolo

Hi Paolo,


On Tue, Nov 29, 2016 at 08:33:20AM +0100, Paolo Greppi wrote:
> I packaged python-jsonref as per this ITP:
> https://bugs.debian.org/844986, this is the repo:
> https://anonscm.debian.org/cgit/python-modules/packages/python-jsonref.git
> 
> Please someone more experienced than me review it and if it's OK sponsor
> its upload.

* git is lacking a pristine-tar branch, please push it (I don't even try
  to build without)
* d/control:
  + please wrap-and-sort that list of build-deps
  + maintainer is you, and DPMT is nowhere to be seen
  + why is Testsuite commented out?
* please bump compat to 10
* d/rules:
  + I think you need to also do --with sphinx to have dh_sphnixdocs do
it's job?
* d/copyright:
  + why are you listing all the files instead of using wildcards?!
  + is there a particular reason the license of debian/ is different and
more stricter than upstream's?
  + no need to repeat "Copyright (C)" on the Copyright: lines
  + also I very much like emails in d/copright
  + the license field of upstream also include the copyright notice, it
shouldn't
* that proxytypes.py has a "based on the implementation..", are you sure
  that's not under a different copyright/license? (if so upstream might
  be at fault here, and this package might not be redistributable)


-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature


PEP 384 (limited ABI)

2016-12-31 Thread Dmitry Shachnev
Hi all, and happy holidays!

The new releases of SIP and PyQt are using the limited set of Python ABI [1]
defined in PEP 384 [2], so that the same .so files work with different Python
versions.

As there seems to be no PEP 384 support in dh_python3, I wonder if I should:

A) Build with only one Python 3 version and install the .so files with
   foo.abi3.so filenames (so no rebuilds will be needed for Python updates);
B) Do not change anything: build for all supported Python 3 versions and
   let dh_python3 rename the files;
C) Anything else?

I could not find any discussion of this PEP in Debian except a couple of
messages from 2010 [3].

[1]: https://www.riverbankcomputing.com/news/sip-419
[2]: https://www.python.org/dev/peps/pep-0384/
[3]: https://lists.debian.org/debian-python/2010/05/msg00103.html

--
Dmitry Shachnev


signature.asc
Description: PGP signature


Bug#849812: ITP: requests-ntlm -- HTTP NTLM authentication using the requests library

2016-12-31 Thread Dominic Hargreaves
Package: wnpp
Severity: wishlist
Owner: Dominic Hargreaves 

* Package name: requests-ntlm
  Version : 1.0.0
  Upstream Author : Ben Toews  et al
* URL : https://github.com/requests/requests-ntlm
* License : ISC
  Programming Lang: Python
  Description : HTTP NTLM authentication using the requests library

HttpNtlmAuth can be used in conjunction with a Session in order to make
use of connection pooling. Since NTLM authenticates connections, this
is more efficient. Otherwise, each request will go through a new NTLM
challenge-response.

This is a new dependency of pywinrm, and will be maintained as part of
the Python Modules Team.



Re: PEP 384 (limited ABI)

2016-12-31 Thread Stefano Rivera
Hi Dmitry (2016.12.31_18:07:17_+0200)

cffi modules will also now use the limited ABI, where possible, so I've
played with them a bit.

> A) Build with only one Python 3 version and install the .so files with
>foo.abi3.so filenames (so no rebuilds will be needed for Python updates);

I think dh_python3 already has the necessary support for that.

Just one thing to watch out for: python3-dbg builds will also use
abi3.so, but aren't actually compatible.

https://bugs.python.org/issue28401

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272