Re: Multiple copies of timeoutsocket.py in Debian packages

2014-01-30 Thread Olivier Berger
Hi.

Jakub Wilk  writes:

> * Olivier Berger , 2014-01-29, 10:25:
>>>Yeah, timeoutsocket.py looks like something that should have died a 
>>>decade ago. In Python ≥ 2.3 you can set default timeout or a 
>>>per-socket timeout without help of this library.
>>>
>>>planet-venus, python-feedvalidator and rawdog already use the proper 
>>>Python interfaces, and only fall back to timeoutsocket when they are 
>>>not available:
>>>http://sources.debian.net/src/python-feedvalidator/0~svn1022-2/feedvalidator/__init__.py#L8
>>>http://sources.debian.net/src/planet-venus/0~git9de2109-1/planet/spider.py#L378
>>>http://sources.debian.net/src/rawdog/2.13.dfsg.1-1/rawdoglib/feedparser.py#L103
>>>
>>
>>I'm wondering, in similar cases, if there is anything that should be 
>>done for these packages, like patching the code to remove the embedded 
>>copy and get rid of the import check, since our Python versions in 
>>Debian are recent enough ? This would eliminate uncertainty...
>
> I would remove the embedded copy from Debian binary packages, and then 
> poke upstream to drop the obsolete code…
>
>>or maybe things should just be kept in the current state... Maybe 
>>that's not worth the worry in general.
>
> … but others' laziness may vary. :-P

Thanks for your suggestions.

Filed the following wishlists (planet-venus already addressed in version
in experimental) :
 - python-feedvalidator : #737117
 - rawdog : #737116

>
>>>plucker and spikeproxy would have to be ported to the “new” API.
>>I guess that would be worth a bug report, then ?
>
> I'm glad you volunteered to file them. ;-)
>

DONE : 
 - plucker : #737114
 - spikeproxy : #737113

Best regards,
-- 
Olivier BERGER 
http://www-public.telecom-sudparis.eu/~berger_o/ - OpenPGP-Id: 2048R/5819D7E8
Ingenieur Recherche - Dept INF
Institut Mines-Telecom, Telecom SudParis, Evry (France)


--
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/87eh3pk6pp@inf-8660.int-evry.fr



Python library style guide: Building and installing debug objects (was: Simplified library style guide based on pybuild)

2014-01-30 Thread Ben Finney
Barry Warsaw  writes:

> https://wiki.debian.org/Python/LibraryStyleGuide
>
> Please take a look, edit as necessary or follow up here for more
> discussion.

I don't see support in there for building and installing debug objects.

Currently we need rules like:

=
.PHONY: build-python%
build-python%:
python$*-dbg setup.py build
python$* setup.py build

.PHONY: override_dh_auto_build
override_dh_auto_build: $(foreach 
pyversion,${PYTHON_VERSIONS},$(pyversion:%=build-python%))
override_dh_auto_build:
dh_auto_build

.PHONY: install-python%
install-python%:
python$*-dbg setup.py install --install-layout=deb \
--root=$(CURDIR)/${package_install_root}
python$* setup.py install --install-layout=deb \
--root=$(CURDIR)/${package_install_root}

.PHONY: override_dh_auto_install
override_dh_auto_install: $(foreach 
pyversion,${PYTHON_VERSIONS},$(pyversion:%=install-python%))
override_dh_auto_install:
dh_auto_install
=

(Or maybe I'm wrong, and there's already a better way to specify in
‘debian/rules’ how to build debug objects for Python extension modules
for each runtime system?)

How should the Python library style guide recommend we do this using
“pybuild”?

-- 
 \ “Welchen Teil von ‘Gestalt’ verstehen Sie nicht?  [What part of |
  `\‘gestalt’ don't you understand?]” —Karsten M. Self |
_o__)  |
Ben Finney


-- 
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/85ob2sj2oo@benfinney.id.au



Re: Indeed, python-concurrent.futures is the same

2014-01-30 Thread Vincent Bernat
[...]

Sandro has orphaned python-concurrent.futures:
 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=736714

Since it is team maintained, I don't think it really makes sense. Should
we just close the bug report and remove Sandro from the Uploaders field?
-- 
panic("Oh boy, that early out of memory?");
2.2.16 /usr/src/linux/arch/mips/mm/init.c


-- 
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/87r47oobvq@guybrush.luffy.cx