On Thu, Jul 2, 2015 at 10:03 PM, Robert Collins
wrote:
> On 3 July 2015 at 11:44, Ian Cordasco wrote:
>> On Thu, Jul 2, 2015 at 6:40 PM, Ben Finney
>> wrote:
>>> Barry Warsaw writes:
>>>
[…] there's actually no reason to have a Python 3 version of enum in
any version >= Python 3.4. [
On 3 July 2015 at 15:05, Ian Cordasco wrote:
> On Thu, Jul 2, 2015 at 10:03 PM, Robert Collins
> wrote:
>> On 3 July 2015 at 11:44, Ian Cordasco wrote:
>>> On Thu, Jul 2, 2015 at 6:40 PM, Ben Finney
>>> wrote:
Barry Warsaw writes:
> […] there's actually no reason to have a Pytho
On 3 July 2015 at 11:44, Ian Cordasco wrote:
> On Thu, Jul 2, 2015 at 6:40 PM, Ben Finney wrote:
>> Barry Warsaw writes:
>>
>>> […] there's actually no reason to have a Python 3 version of enum in
>>> any version >= Python 3.4. […]
>>
>> Ian Cordasco writes:
>>
>>> Probably a silly question, bu
On 3 July 2015 at 11:40, Ben Finney wrote:
> Barry Warsaw writes:
>
>> […] there's actually no reason to have a Python 3 version of enum in
>> any version >= Python 3.4. […]
>
> Ian Cordasco writes:
>
>> Probably a silly question, but are other libraries like unittest2 also
>> being packaged for
On 3 July 2015 at 09:53, Ian Cordasco wrote:
> On Thu, Jul 2, 2015 at 2:55 PM, Barry Warsaw wrote:
>> As part of the 3.5 test rebuild I noticed an incompatibility with
>> python3-enum, which I reported upstream. The response was: there's actually
>> no reason to have a Python 3 version of enum i
On Thu, Jul 2, 2015 at 6:40 PM, Ben Finney wrote:
> Barry Warsaw writes:
>
>> […] there's actually no reason to have a Python 3 version of enum in
>> any version >= Python 3.4. […]
>
> Ian Cordasco writes:
>
>> Probably a silly question, but are other libraries like unittest2 also
>> being packa
Barry Warsaw writes:
> […] there's actually no reason to have a Python 3 version of enum in
> any version >= Python 3.4. […]
Ian Cordasco writes:
> Probably a silly question, but are other libraries like unittest2 also
> being packaged for python3? Another library is mock. That was included
>
On Thu, Jul 2, 2015 at 2:55 PM, Barry Warsaw wrote:
> As part of the 3.5 test rebuild I noticed an incompatibility with
> python3-enum, which I reported upstream. The response was: there's actually
> no reason to have a Python 3 version of enum in any version >= Python 3.4.
> Since that's all we
As part of the 3.5 test rebuild I noticed an incompatibility with
python3-enum, which I reported upstream. The response was: there's actually
no reason to have a Python 3 version of enum in any version >= Python 3.4.
Since that's all we have now, maybe it makes more sense to just remove the
python
hi all,
i would like to join the python modules team, mainly to maintain a few
python-modules (who would have guessed that?), that I need as
dependencies for other packages I maintain.
I'm a long-term Debian user, and have become involved in packaging as
late as ~2010, when I joined the pkg-multi
Hi Tomasz,
On Tue, 30 Jun 2015 21:59:00 +0200, Tomasz Rybak wrote:
> According to Sphinx documentation
> http://sphinx-doc.org/config.html#confval-html_last_updated_fmt
> when "html_last_updated_fmt" is set, "Last updated on ..." should
> be added to the bottom. Is this omission on purpose, or doe
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi All
I've been skulking around on this ML and on the #debian-python IRC
channel for a while now so thought it was about time I put in my
request to join the DPMT.
I've been working across Debian and Ubuntu for the last 4.5 years; I
started doing
Hello,
My name is Corey Bryant. https://alioth.debian.org/users/coreycb-guest
I'm writing to request membership to the DPMT team.
I primarily work on OpenStack packaging and with that comes the need to
touch some of the python packages that do not fall under the openstack
team. For example I c
13 matches
Mail list logo
