Re: Update of python-xlwt with Py3 support
On Wed, Oct 25, 2017 at 08:02:57PM +0200, Thomas Goirand wrote: > Hi Jan, > > I've pushed to the git a new branch called new-upstream-1.3.0, which > adds Python 3 support, and some improvements to the package. Here's the > debian/changelog: > > * New upstream release. > * Ran wrap-and-sort -bast to minimize git diffs. > * Add Python 3 support. > * Tests with nose. > * Add a doc package and generate the doc using sphinx. > * Generate the doc using sphinx. > * Fixed dh sequencer call order. > * Standards-Version is now 4.1.1. > > Could you please have a look, and let me know if you're OK for me to > upload that? Hi Thomas, thank you very much for your work. The changes look good to me, please merge them to the master branch and go forward with the upload. Kind regards Jan -- Jan Dittberner - Debian Developer GPG-key: 4096R/0xA73E008FB8DD 2009-05-10 B2FF 1D95 CE8F 7A22 DF4C F09B A73E 0055 558F B8DD https://portfolio.debian.net/ - https://people.debian.org/~jandd/
Re: Python and Debian infrastructure
On Thu, Apr 16, 2015 at 02:30:16PM +0200, Nicolas Chauvat wrote: > On Thu, Apr 16, 2015 at 02:58:53PM +0800, Paul Wise wrote: > > Port services based on Pylons (deprecated) to something else like Django: > > Pylons is deprecated in favor of Pyramid. It could be that porting > these services to Pyramid will be easier than rewriting on top of Django. I already plan to port my debianmemberportfolio service to Python3 and Pyramid or Django later this year. I have experience with both but think that Pyramid is a bit more lightweight and I don't need a ORM and many other Django features. Paul already suggested to merge debianmemberportfolio with db.debian.org but I did not have time to evaluate that option yet. Best regards Jan -- Jan Dittberner - Debian Developer GPG-key: 4096R/558FB8DD 2009-05-10 B2FF 1D95 CE8F 7A22 DF4C F09B A73E 0055 558F B8DD https://jan.dittberner.info/ signature.asc Description: Digital signature
Re: python3 celery
On Mon, Jul 14, 2014 at 02:09:36PM +1000, Brian May wrote: > Hello, > > Anybody interested in helping out with getting Celery Python3 packages into > Debian? > > There seems to be a long list of dependencies that need to be dealt with > first, > and a lot of these are maintained by individuals, not the Python team. > > e.g. celery itself build-depends on: > ... > Depends: python3-pika but it is not > installable Hello Brian, python-pika depends on Twisted which is Python 2 only, upstream supports Python 2 only too. The Pika documentation has a statement "Currently pika only supports Python 2.6 and 2.7. Work to support 3.3+ is underway." Best regards Jan -- Jan Dittberner - Debian Developer GPG-key: 4096R/558FB8DD 2009-05-10 B2FF 1D95 CE8F 7A22 DF4C F09B A73E 0055 558F B8DD http://www.dittberner.info/ signature.asc Description: Digital signature
Re: orphaning the turbogears stack
On Wed, 1 Feb 2012 19:06:24 Stefano Zacchiroli wrote: > Heya, > I've just uploaded to DELAYED/5 the following (source) packages, > orphaning each of them: > > python-repoze.tm2 ... I just adopted python-repoze.tm2. Kind regards Jan -- Jan Dittberner - Debian Developer GPG-key: 4096R/558FB8DD 2009-05-10 B2FF 1D95 CE8F 7A22 DF4C F09B A73E 0055 558F B8DD http://ddportfolio.debian.net/ - http://people.debian.org/~jandd/ signature.asc Description: Digital signature
Re: RFS: python-crypto (adopting package)
On Mon, May 09, 2011 at 09:40:58AM +0200, Sebastian Ramacher wrote: > Hi, > > I am looking for a sponsor for the new version 2.3-1 of my package > "python-crypto". > > It builds these binary packages: > python-crypto - cryptographic algorithms and protocols for Python > python-crypto-dbg - cryptographic algorithms and protocols for Python (debug > extensio > python-crypto-doc - cryptographic algorithms and protocols for Python > (documentation) > > The package appears to be lintian clean. > > The upload would fix these bugs: 532121, 617001, 625238 > > The package can be found in the svn repository at > svn+ssh://svn.debian.org/svn/python-modules/packages/python-crypto > > I would be glad if someone uploaded this package for me. I'm interested in python-crypto and will have a look at your packaging later today. If everything is fine I'll upload it. Regards Jan -- Jan Dittberner - Debian Developer GPG-key: 4096R/558FB8DD 2009-05-10 B2FF 1D95 CE8F 7A22 DF4C F09B A73E 0055 558F B8DD http://www.dittberner.info/ signature.asc Description: Digital signature
Re: RFS: pybtex
On Mon, Apr 18, 2011 at 04:41:27PM +0200, Daniel Stender wrote: > Hi people, > > I would like to refresh my RFS for Pybtex. Isn't there anybody with a little > time ...? Hi Daniel, I'll have a look at it. Regards Jan > Greetings, > Daniel Stender > > On 15.03.2011 16:46, Daniel Stender wrote: > > Hi guys, > > > > I would like to refresh my request for sponsorship towards Pybtex 0.15-1 > > after RFA. Please check it as usual at Alioth: > > http://svn.debian.org/wsvn/python-apps/packages/pybtex -- Jan Dittberner - Debian Developer GPG-key: 4096R/558FB8DD 2009-05-10 B2FF 1D95 CE8F 7A22 DF4C F09B A73E 0055 558F B8DD http://www.dittberner.info/ signature.asc Description: Digital signature
Re: Talk on Debian packaging of Python, Python modules and Python extensions at PyCon DE
On Mon, Mar 28, 2011 at 12:41:30PM +0200, Piotr Ożarowski wrote: > [Jan Dittberner, 2011-03-28] > > The organizers are especially interested in best practice recommendations > > for > > Python developers to make the life of packagers easier. > > http://us.pycon.org/media/2010/talkdata/PyCon2010/038/paper.html#good-practices > http://wiki.debian.org/UpstreamGuide > http://www.python.org/dev/peps/pep-0386/ > http://mail.python.org/pipermail/python-dev/2010-April/099729.html Hello, thanks for the links. I think this is enough information for the Python modules/extensions part. Regards Jan -- Jan Dittberner - Debian Developer GPG-key: 4096R/558FB8DD 2009-05-10 B2FF 1D95 CE8F 7A22 DF4C F09B A73E 0055 558F B8DD http://ddportfolio.debian.net/ - http://people.debian.org/~jandd/ signature.asc Description: Digital signature
Talk on Debian packaging of Python, Python modules and Python extensions at PyCon DE
Dear Debian Python people,
at Chemnitzer Linux-Tage [1] I talked to some guys who are organizing the first
PyCon DE [2] which will take place in Leipzig, Germany in October. They are
quite interested to get a talk on Debian packaging of Python, Python modules
and extensions. I would like to prepare and hold such a talk but would like
your feedback/input on what you would like to tell the Python development
community.
The organizers are especially interested in best practice recommendations for
Python developers to make the life of packagers easier.
They also asked me how Python itself is packaged. I will have a look at the
packaging but some kind of short summary of the most important things from your
perspective would be great.
I would like to give some best practice statements for Python module, Python
extension and Python application packaging too. From my point of view this
would include dh and dh_python{2,3}. I know there is cdbs and python-support
does exist too, should I include them?
I will suggest interested people to join DPMT, PAPT, debian-python@l.d.o and
tell them about #debian-python too.
Do you have more ideas about what should be said (or not said) there?
[1] http://wiki.debian.org/DebianEventsChemnitzerLinuxTage2011
[2] http://de.pycon.org/
Regards
Jan
--
Jan Dittberner - Debian Developer
GPG-key: 4096R/558FB8DD 2009-05-10
B2FF 1D95 CE8F 7A22 DF4C F09B A73E 0055 558F B8DD
http://ddportfolio.debian.net/ - http://people.debian.org/~jandd/
signature.asc
Description: Digital signature
Re: E: dh_python2:146: you most probably have to build extension for python2.5.
On Thu, Mar 10, 2011 at 09:03:03PM +0100, Ludovic Rousseau wrote: > Hello, > > I moved my package pykcs11 [1] from dh_pycentral to dh_python2. The > conversion was easy. The version in unstable uses dh_python2. > > I also wanted to move my debian/rules file from the "heavy" version > [2] to the minimal version using: > > #!/usr/bin/make -f > %: > dh $@ --with python2 > > But I now get a warning and an error (complete log attached): > [...] >dh_python2 > W: dh_python2:94: Python 2.6 should install files in > /usr/lib/python2.6/dist-packages/. Did you forget > "--install-layout=deb"? > E: dh_python2:146: you most probably have to build extension for python2.5. > make: *** [binary] Error 12 you might want to add override_dh_auto_build: python setup.py install --root=$(CURDIR)/debian/python-pykcs11 --install-layout=deb (The important part is --install-layout=deb). Regards Jan -- Jan Dittberner - Debian Developer GPG-key: 4096R/558FB8DD 2009-05-10 B2FF 1D95 CE8F 7A22 DF4C F09B A73E 0055 558F B8DD http://ddportfolio.debian.net/ - http://people.debian.org/~jandd/ signature.asc Description: Digital signature
Re: Switching to git
On Sun, Mar 06, 2011 at 01:33:45PM -0500, Barry Warsaw wrote: > On Mar 06, 2011, at 05:43 PM, Sandro Tosi wrote: > > >Do the 2 VCDs you mentioned have clear advantage that make then > >preferible to git except being Python-based? If so, I think it's a > >quite weak reason. > > Let me turn that around: why would you *not* want to use a Python based dVCS? > I think Debian package maintainer tool support should be considered. > One reason could be that git is the de-facto standard for Debian. I guess > choice of dVCS is the editor-wars of the 2010s, and probably just as silly. Is there a mature git-buildpackage replacement for mercurial or bazaar? There is a mercurial-buildpackage but I don't know how feature complete/ comparable to git-buildpackage or svn-buildpackage it is. How well does debcommit work with mercurial or bazaar? Regards Jan -- Jan Dittberner - Debian Developer GPG-key: 4096R/558FB8DD 2009-05-10 B2FF 1D95 CE8F 7A22 DF4C F09B A73E 0055 558F B8DD http://www.dittberner.info/ signature.asc Description: Digital signature
Re: Python 2.7 in, Python 2.5 out, dh_python2
On Mon, Feb 07, 2011 at 10:27:06AM +0100, Piotr Ożarowski wrote:
> Hi,
>
> We plan to upload new python-defaults to unstable really soon now
> (once python2.7 will be available for all architectures in unstable).
>
> Instead of Python 2.5, it will list Python 2.7 as supported
> (default=2.6; supported=2.6,2.7).
>
> Once Python 2.7 will be well supported¹ in the archive, Python 2.6 will
> be dropped as well so that Wheezy will support only one Python 2.X version
> (the last one ever released upstream).
+1
> No, that's not meant to make security team's life easier, it's a tricky
> way to force the usage of my dh_python2 helper and get rid of
> python-{central,support} ;-)
great plan :-)
Regards
Jan
--
Jan Dittberner - Debian Developer
GPG-key: 4096R/558FB8DD 2009-05-10
B2FF 1D95 CE8F 7A22 DF4C F09B A73E 0055 558F B8DD
http://ddportfolio.debian.net/ - http://people.debian.org/~jandd/
signature.asc
Description: Digital signature
Re: Possible Mass Bug Filing: String Exceptions Removed in Python 2.6
On Sat, Jun 05, 2010 at 10:43:27PM -0400, Scott Kitterman wrote: > As was recently discussed on debian-python: > > http://lists.debian.org/debian-python/2010/05/msg00111.html > > String exceptions are no longer supported at all in Python 2.6. Since this > is > the Python version planned to be the default in Squeeze, packages still using > them should be fixed. String exceptions have never worked reliably or been a > good idea. It is time for them to go. > > A couple of weeks ago, Jakub Wilk noticed this issue and prepared both a DD > list of affected packages and the grep output that was used to detect > potentially affected packages. I know some of these packages have been fixed > already. Please reply to debian-python with fix reports or reports of false > positives. > > http://people.debian.org/~jwilk/tmp/string-exceptions.ddlist > > http://people.debian.org/~jwilk/tmp/string-exceptions.log I will have a look at the ldaptor string exceptions (most of them are raise "TODO" and may be better expressed with NotImplementedError). Regards Jan -- Jan Dittberner - Debian Developer GPG-key: 4096R/558FB8DD 2009-05-10 B2FF 1D95 CE8F 7A22 DF4C F09B A73E 0055 558F B8DD http://ddportfolio.debian.net/ - http://people.debian.org/~jandd/ signature.asc Description: Digital signature
Re: Request for review / sponsorship for jsonpickle
On Sun, Dec 13, 2009 at 04:26:49PM -0600, John Paulett wrote: > Hello, > > I uploaded my first Debian package, jsonpickle, to mentors.debian.org > (http://mentors.debian.net/cgi-bin/sponsor-pkglist?action=details;package=jsonpickle). > jsonpickle is a library that builds on top of the existing Python > JSON encoders (simplejson, stdlib json, demjson) by allow more complex > object graphs to be serialized to JSON. I would greatly appreciate > any comments and suggestions on this package. > > I tried to follow the Debian and Python packaging guidelines and > examined the packaging of several other Python packages, so hopefully > the jsonpickle package is close to being acceptable. Would you mind maintaining it in the DPMT (Debian Python Modules Team) [1] colaboratively? This would give you a better chance for sponsored uploads. [1] http://python-modules.alioth.debian.org/ Regards Jan Dittberner -- Jan Dittberner - Debian Developer GPG-key: 4096R/558FB8DD 2009-05-10 B2FF 1D95 CE8F 7A22 DF4C F09B A73E 0055 558F B8DD http://www.dittberner.info/ signature.asc Description: Digital signature
Re: Trac team almost dead?
On Fri, Aug 28, 2009 at 10:48:48AM +0200, W. Martin Borgert wrote: > On 2009-08-26 10:59, Alexander GQ Gerasiov wrote: > > project on alioth looks nearly dead. We're using trac actively in our > > lab, so I'll think about entering team to help them a little bit. > > I wonder, how people feel about moving Trac from its own team > to a larger, more active team, i.e. Debian Python Modules Team, > which already has some of tracs dependencies, i.e. > libapache2-mod-python, mod-wsgi, python-docutils, genshi, > python-mysqldb, and pygments. If nobody objects, I would do the > necessary work, including fix of #521513 (i.e. upload of current > trac version 0.11.5), under the flag of the python-modules team. > > Andres, Federico, Jesus, Luis, Otavio, what do you think? I would really like to have trac in DPMT (or more activity in the current trac team). Maybe we could also coordinate to include commithooks [1] which integrate darcs, mercurial and git with trac and debbugs but should use trac's included post-commit scripts and consists of some Python and bash scripts. [1] http://git.complete.org/commithooks I'm using trac and commithooks and would like to help with better Debian support for both. Regards Jan -- Jan Dittberner - Debian Developer GPG-key: 4096R/558FB8DD 2009-05-10 B2FF 1D95 CE8F 7A22 DF4C F09B A73E 0055 558F B8DD http://ddportfolio.debian.net/ - http://people.debian.org/~jandd/ signature.asc Description: Digital signature
Re: ldaptor in DPMT: anyone interested?
On Mon, Mar 09, 2009 at 12:41:58PM +0100, Sandro Tosi wrote: > Hello, > anytime soon (== when I'll find some time to work on it) I'll have to > do a QA upload for ldpator[1] (a couple of bugs need to be fixed: > pysupport and pyopenssl transition). > > [1] http://packages.qa.debian.org/l/ldaptor.html > > So I'm wondering if anyone is interested to maintain it in the DPMT > (it seems mainly a module, only inferred from its PTS page and popcon > ;) ); in that case, we can work together and sponsorship is free :) > > Let me know asap. Hi Sandro, I'm interested and use this module for a current development. Regards Jan PS: I got my AM approval on Saturday and wait for FD/DAM now -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: #510782 - python-excelerator: debian/copyright fails to mention copyright for antlr.py
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sun, Jan 11, 2009 at 05:42:28PM +0100, Wouter van Heyst wrote: > On Mon, Jan 05, 2009 at 08:58:53PM +0100, Evgeni Golov wrote: > > Hi *, > > > > while looking at rc bugs, I stumbled over this one and thought I can fix > > it. You can find a proposed NMU debdiff attached. It adds the needed > > bits to debian/copyright, stops installing antlr.py and adds a > > ... > > > Dear Debian Python people, do you have an oppinion on that? > > Shipping an own antlr.py is imho an security issue, so we should try to > > avoid that in any case (or get another RC as soon this issue is > > "solved"). > > Only that pyExcelerator is rather obsoleted by xlwt. Unforunately, that > isn't packaged, it should be. xlwt is in NEW since Wednesday (2009/01/07) [1], [2] [1] http://ftp-master.debian.org/new/xlwt_0.7.0-1.html [2] http://ftp-master.debian.org/new/xlwt_0.7.0-2.html If it's accepted I'll add work on the transition from pyexcelerator. This will not fix the bug for Lenny though. Regards Jan -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAklqKZgACgkQXZJ0m2XDVK9dEgCfRtanuAT9HoNKdtISbVJr894H pdwAn2C713iKx4nuc/hnb4pv/N0/jVs1 =2LyN -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: numpy 1.2.1, switching to git?
On Mon, Dec 22, 2008 at 09:04:33AM +1100, Ben Finney wrote: > Cyril Brulebois writes: > > > Tristan Seligmann (20/12/2008): > > > My personal preference ordering would probably be: > > > > > > hg, bzr, svn, git git, bzr, svn I read some git stuff today and think it's superior to the other VCSs I know. Jan signature.asc Description: Digital signature
I want to join the Python Modules Packaging Team
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello, Piotr Ożarowski asked me to consider joining your team. I maintain the package python-migrate (a database schema migration tool for sqlalchemy) and would like to maintain the package together with you. I'm not a DD and my alioth login is jandd-guest. Regards Jan -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHttYgXZJ0m2XDVK8RAoRZAJ0e2Iu7tKq0c2LmWnDu1RC5/qnijgCfRUPp VsJutEn7uFummgPZYL0D3hY= =9KL5 -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
