[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#736523: marked as done (ITP: python-future -- backport of the concurrent.futures package)

Your message dated Wed, 05 Feb 2014 13:44:25 +0800
with message-id <52F1CFB9.1040701@debian.org>
and subject line Re: Bug#736523: python-future name clobbers existing Python package
has caused the Debian Bug report #736523,
regarding ITP: python-future -- backport of the concurrent.futures package
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
736523: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=736523
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: wnpp
Severity: wishlist
Owner: Thomas Goirand <zigo@debian.org>

* Package name    : python-future
  Version         : 2.1.6
  Upstream Author : Alex Gronholm <alex.gronholm+pypi@nextday.fi>
* URL             : https://pypi.python.org/pypi/futures
* License         : BSD-2-clause
  Programming Lang: Python
  Description     : backport of the concurrent.futures package

 This package is a backport of concurrent.futures from Python 3.2 to Python
 2.6, 2.7 and 3.1. In Debian, there is no use of Python 3.1 support anymore,
 and only 2.7, and to some extend 2.6 (for backports), is useful.

--- End Message ---
--- Begin Message --- 
On 02/05/2014 06:29 AM, Javier Candeira wrote:
> Regardless of the status of concurrent.futures, there is an issue of
> consistency with the 'python-future' package name. There is already a
> 'future' package for python [1, 2], and the naming convention
> established in the Debian Python policy [3] would make users expect
> this package be available as 'python-future'.
> 
> [1]  http://python-future.org/
> 
> [2] https://pypi.python.org/pypi/future
> 
> [3] http://www.debian.org/doc/packaging-manuals/python-policy/ch-module_packages.html#s-package_names
> 
> JC

Hi,

FYI, this was a mistake from my side. We shouldn't do a mistake between:

https://pypi.python.org/pypi/future
and
https://pypi.python.org/pypi/futures

(notice the last char...)

By the way, what I needed was futures (with s at the end), which is part
of concurrent.futures. So this ITP can be closed.

Cheers,

Thomas

--- End Message ---
Reply to: