Re: Sympy 0.7.2
* Dmitry Shachnev mity...@gmail.com, 2012-10-29, 14:47: 2. dh_sphinxdoc should handle URLs starting with a protocol name correctly (so that it won't complain about .../html/file:///usr/share/javascript/mathjax/MathJax.js?config=TeX-AMS_HTML-full missing) This is now fixed in svn. 3. It would be also good if dh_sphinxdoc stripped everything after ? character. Ditto. -- Jakub Wilk -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20121108133234.ga1...@jwilk.net
Re: Advise on packaging a new Python module
Hi, On Wed, Nov 07, 2012 at 12:30:41PM +0100, Tomás Di Domenico wrote: Thank you very much for your input, Jakub and Dmitry. I'll start working on those changes right away. And yes, it would be very nice to try and get a Python3 version up. In fact, I'm quite interested in learning how to manually write the code, without dh (though I foresee it will take me some time ;). As far as I have followed this thread I have not seen an answer to this part of your mail. I admit I have no idea how to support Python 2 *and* 3 but wild-guessing from my experience with Debian tools I doubt any manual code writing would be needed. Any more detailed advise? Kind regards Andreas. -- http://fam-tille.de -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20121108141530.go17...@an3as.eu
Re: Advise on packaging a new Python module
On 8 November 2012 14:15, Andreas Tille andr...@an3as.eu wrote: As far as I have followed this thread I have not seen an answer to this part of your mail. I admit I have no idea how to support Python 2 *and* 3 but wild-guessing from my experience with Debian tools I doubt any manual code writing would be needed. Any more detailed advise? Some manual code writing is needed, as debhelper doesn't yet know how to automatically build packages with Python 3. The best description is this wiki page: http://wiki.debian.org/Python/LibraryStyleGuide Thomas
Re: Advise on packaging a new Python module
Thanks, Thomas, that's a great resource. I had been looking at some files from existing Python 3 packages, but that makes it clearer. I'll now focus on wrapping up the Python 2 package, and then I'll move on to the Python 3 version. Thanks again! On 08/11/12 15:28, Thomas Kluyver wrote: On 8 November 2012 14:15, Andreas Tille andr...@an3as.eu mailto:andr...@an3as.eu wrote: As far as I have followed this thread I have not seen an answer to this part of your mail. I admit I have no idea how to support Python 2 *and* 3 but wild-guessing from my experience with Debian tools I doubt any manual code writing would be needed. Any more detailed advise? Some manual code writing is needed, as debhelper doesn't yet know how to automatically build packages with Python 3. The best description is this wiki page: http://wiki.debian.org/Python/LibraryStyleGuide Thomas -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/509bcdac.3060...@tdido.com.ar
pyxs review
Maykel Moya asked to join DPMT. Here's my preliminary review of pyxs, the package he wants to maintain within the team. (Note that I don't intend to sponsor this, sorry!) I downloaded the package from: http://mentors.debian.net/debian/pool/main/p/pyxs/pyxs_0.3+git20111205.793e02c0-2.dsc There are two technical problems with your repacked .orig.tar: - You should not include the .git directory. - There should be a single top-level directory, so that the tarball can be easily extracted manually. If you don't use prisite upstream tarballs, debian/rules should have a get-orig-source target. I see that the tarball now includes the LGPL license. This is good, but note that it's not a standalone license; it's merely a set of extra permissions to the GPL license. Please ask upstream to include GPL license in their VCS/tarballs, too. runtests.py contains a gigantic pickled blob. I suppose it contains pytest code (though I don't know for sure; there's no easy and secure way to unpickle stuff!). If this is the case, that'd violation of DFSG§2. Now some less severe problems: I'd advise you not to use a more restrictive license than upstream uses. Current standards version is 3.9.4 (but note that lintian is now aware of it yet). Upstream provides documentation, it would be a good idea to build and install it into the binary package. I see there are also some examples in the tarball; it might be worth shipping them in .deb, too. Upstream includes a test suite. Please run it at build time, ideally using all supported Python versions. You might want also provide DEP-8 tests. lintian emits: I: python-pyxs: description-synopsis-might-not-be-phrased-properly I: python-pyxs: extended-description-is-probably-too-short lintian4python emits: i: pyxs source: python-stdeb-boilerplate debian/rules:3 This file was automatically generated by stdeb 0.6.0+git e: python-pyxs: pyflakes-undefined-name usr/share/pyshared/pyxs/_compat.py:74: Monitor -- Jakub Wilk -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20121108220804.ga6...@jwilk.net
