Re: How to solve #751375, file clash
On 16 October 2014 23:55, Brian May br...@microcomaustralia.com.au wrote: Is the configparser.py supplied by python-pies2overrides different from the file supplied by python-configparser? If it is the same file, you could delete it from python-pies2overrides and depend on python-configparser. The pies2overrides configparser.py contains only this: == from __future__ import absolute_import from ConfigParser import * == (The purpose of the pies2overrides library is to provide compatibility with Python 3 stdlib names) I would guess that using python-configparser in place of this module would still work, at least for the software that uses pies2overrides. On 16 October 2014 23:49, Per Andersson avtob...@gmail.com wrote: or to move pies2overrides into it's own namespace (and patch frosted accordingly)? If you're planning to patch frosted (or any other software that uses pies2overrides; I packaged and uploaded isort recently, for example), then there's not much point in *moving* pies2overrides, just patch the software not to use it at all. That is, there is no point writing this: try: from configparser import blah except ImportError: from pies2overrides.configparser import blah Instead of just writing this: try: from configparser import blah except ImportError: from ConfigParser import blah -- mithrandi, i Ainil en-Balandor, a faer Ambar -- 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/camckhmsc6+hzdz2swkagq0c7j5iy00byyo5ouf_hsnt69cp...@mail.gmail.com
Re: Keeping upstream commits separate from Debian packaging commits
On 16 October 2014 20:12, Hans-Christoph Steiner h...@at.or.at wrote: Tristan Seligmann wrote: If you are fetching the upstream revisions / tags into your packaging repository, you can use the upstream tag exactly as-is, no need to re-tag (and indeed re-tagging would generally be a bad idea). I think there is a lot of value to always including the Debian upstream/v1.0 tag. It provides a standard way to access the upstream version across all repos. There is no such standard out there in the wild. There are tags like v1.0, 1.0, release-1.0, the-real-1.0, etc. etc. Renaming the tag does not require retagging, git tag objects (perhaps unfortunately) do not include their name. -- mithrandi, i Ainil en-Balandor, a faer Ambar -- 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/CAMcKhMTEMf8MgvaQB476mvG_=kz7mhalfbxv1bd9_zuouaj...@mail.gmail.com
Status of pythondialog in Debian
Hello, As the upstream maintainer of pythondialog, I feel a bit concerned about its status in Debian, in particular about what is going to go into jessie. In short, I'd rather see the package removed from Debian than stay in the current status. The package that is currently in unstable is terribly outdated (the version dates from 2004), has a few bugs, supports neither Unicode correctly nor Python 3, contrary to current upstream versions, not to mention a bunch of features including help and extra button support, easy pythondialog and backend version checking, autowidgetsize and the new Sphinx-generated manual[1]. In case someone is interested, I've prepared a package of the latest version for Python 3, using dh, dh_python3 and pybuild, following the suggestions given on the Debian Python wiki (which is nice to have, thank you!). It has been built on current sid and is available in the following GPG-signed APT repository: deb http://people.via.ecp.fr/~flo/debian unstable main deb-src http://people.via.ecp.fr/~flo/debian unstable main (along with other packages, don't upgrade blindly if you add the repository to your sources.list) Thanks [1] http://pythondialog.sourceforge.net/doc/ -- Florent -- 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/871tq62320@frougon.crabdance.com
Re: Status of pythondialog in Debian
Hi Florent, On Oct 17, 2014, at 04:17 PM, Florent Rougon wrote: As the upstream maintainer of pythondialog, I feel a bit concerned about its status in Debian, in particular about what is going to go into jessie. In short, I'd rather see the package removed from Debian than stay in the current status. Please note that this is not a team-maintained package. We could do a non-maintainer upload of it, but I'd rather see either 1) Adam, the current maintainer CC'd here, update the package, or 2) have Adam move the package to the Debian Python team, where we could collectively maintain it going forward. The package that is currently in unstable is terribly outdated (the version dates from 2004), has a few bugs, supports neither Unicode correctly nor Python 3, contrary to current upstream versions, not to mention a bunch of features including help and extra button support, easy pythondialog and backend version checking, autowidgetsize and the new Sphinx-generated manual[1]. In case someone is interested, I've prepared a package of the latest version for Python 3, using dh, dh_python3 and pybuild, following the suggestions given on the Debian Python wiki (which is nice to have, thank you!). That's excellent, thanks, and should help us (either the team or Adam) update the package. Would you be able to file a bug on the package in Debian, and attach a diff (debdiff) of your packaging changes? https://bugs.debian.org/cgi-bin/pkgreport.cgi?dist=unstable;package=python-dialog Cheers, -Barry -- 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/20141017110335.50d2a...@anarchist.wooz.org
