Re: DKIM RFS: mistune -- Markdown parser in pure Python
Hi, Le 20/05/2015 09:16, Julien Puydt a écrit : I have now made my package for mistune in the python-modules/ directory on alioth. I used git like for my debian-science packages, since this team's policy is moving in that direction too. Mistune is a fast markdown parser in pure Python, and is a required dep of ipython 3/jupyter, which was a motivation to package it. Some other trivia : Homepage: https://github.com/lepture/mistune Vcs-Git: git://anonscm.debian.org/python-modules/packages/mistune.git Vcs-Browser: http://anonscm.debian.org/gitweb/?p=python-modules/packages/mistune.git Copyright: 2014-2015 Hsiaoming Yang License: BSD-3-clause I need someone to mentor me on this first DPMT package, and if things look neat enough, sponsor an upload to unstable. This is still current. Snark on #debian-python -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/557afddb.3080...@laposte.net
Re: RFS: python-tornado -- scalable, non-blocking web server and tools
Hi, Le 20/05/2015 17:18, Julien Puydt a écrit : this package already exists in debian ; in fact, the DPMT's svn had 3.2.2-1, debian had 3.2.2-1.1 (a NMU for a *team* package... strange idea), upstream has put 4.1.0 out with 4.2.0 to come [4.2.0.b1 is out, so it's still interesting to work on 4.1.0]. I did the following : - I pushed the changes from 3.2.2-1.1 in DPMT's svn repository ; - I updated the DPMT's svn repository for a 4.1.0-1 : (-) removed outdated patches ; (-) refreshed old patches ; (-) added a patch so we use debian's ca-certificates (instead of a new dep on a certifi package which looks for them around) (-) pushed standards-version up (-) add ca-certificates as a build-dep so tests pass at build-time (-) add myself to uploaders so it's not an NMU (I'm now part of the team, thanks!) (-) updated d/ch to document the above. Hopefully that didn't break anything... Now I need someone to mentor the changes since I'm not an old-timer in DPMT and a sponsor for an upload. Still current, Snark on #debian-python -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/557afd84.7040...@laposte.net
Re: DKIM RFS: ptyprocess -- Run a subprocess in a pseudo terminal from Python
Hi, Le 03/06/2015 20:40, Julien Puydt a écrit : * Package name : ptyprocess Version: 0.5 Upstream author: Thomas Kluyver tho...@kluyver.me.uk * URL: https://github.com/pexpect/ptyprocess License: ISC Description: Run a subprocess in a pseudo terminal in Python Launch a subprocess in a pseudo terminal (pty), and interact with both the process and its pty. Sometimes, piping stdin and stdout is not enough. There might be a password prompt that doesn't read from stdin, output that changes when it's going to a pipe rather than a terminal, or curses-style interfaces that rely on a terminal. If you need to automate these things, running the process in a pseudo terminal (pty) is the answer. It is a dependency for terminado (RFP #787201), on which ipython's newer version (#780408) depends in its turn for its notebook. I have a package ready for review at the usual place: Vcs-Git: git://anonscm.debian.org/python-modules/packages/ptyprocess.git Vcs-Browser: http://anonscm.debian.org/gitweb/?p=python-modules/packages/ptyprocess.git Still current, Snark on #debian-python -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/557afd42.7080...@laposte.net
Re: Source package name with python- or without?
Scott Kitterman: On June 9, 2015 9:08:06 AM EDT, Thomas Goirand z...@debian.org wrote: On 06/08/2015 08:13 AM, Piotr Ożarowski wrote: [Tim Landscheidt, 2015-06-08] Should source package names (Source: in debian/control) be prefixed with python-? no. I use python- prefix for source package name only if the name is not unique enough. I have the opposite view, and I very much prefer to prefix with python- all of the source packages I upload, when that's a python module (I don't do that for applications). One very good reason for this is sorting the files when you do ls, or in your QA page, on gitweb/cgit, etc. Also, not polluting the general namespace is a good idea. If the upstream name isn't python-*, then the namespace is already polluted. Personally, I think upstream name for the source package is best unless it's really generic. Scott K I see this two ways: * if the source package only produces a single python- and python3- package, then I make the source package name with python- so that there are fewer names to keep track off, and it is easy to find the source package * if the source package produces more than one python- package and/or more than one python3- package, then I use the source name. .hc -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/557aec5d.70...@at.or.at
