On Friday, May 22, 2015 02:17:59 PM Ian Cordasco wrote:
> On Fri, May 22, 2015 at 10:12 AM, Tristan Seligmann
>
> wrote:
> > On 22 May 2015 at 16:06, Tristan Seligmann
wrote:
> >> Or are you saying that the ipaddress backport is not compatible with
> >> python3 stdlib's ipaddress? (This would b
On Fri, May 22, 2015 at 10:12 AM, Tristan Seligmann
wrote:
> On 22 May 2015 at 16:06, Tristan Seligmann wrote:
>> Or are you saying that the ipaddress backport is not compatible with
>> python3 stdlib's ipaddress? (This would be a very unfortunate state of
>> affairs, but impossible to imagine)
>
On Friday, May 22, 2015 07:08:31 PM Dmitry Shachnev wrote:
> Hi,
>
> On Tue, 19 May 2015 16:51:34 +0200, W. Martin Borgert wrote:
> > In some cases (don't ask me which ones) Debian changes package
> > names on fundamental changes, e.g. from "python-simpy" to
> > "python-simpy3". This allows to upd
Hi,
On Tue, 19 May 2015 10:36:13 -0300, Marcelo Jorge Vieira wrote:
> I am packaging pexif because it is a dependency for Thumbor [0]. My
> question is, pexif has some scripts with generic names [1], like
> 'timezone', should I rename it?
>
> [0] https://github.com/thumbor/thumbor
> [1] https://gi
Hi Mathieu,
On Wed, 20 May 2015 11:57:26 +0200, Mathieu Malaterre wrote:
> [Please CC me]
>
> I am reviewing some python packages. On my jessie machine here is what
> I am seeing:
>
> $ dget -u
> http://mentors.debian.net/debian/pool/main/p/python-udiskie/python-udiskie_1.1.2-1.dsc
> $ cd python-
Hi,
On Tue, 19 May 2015 16:51:34 +0200, W. Martin Borgert wrote:
> In some cases (don't ask me which ones) Debian changes package
> names on fundamental changes, e.g. from "python-simpy" to
> "python-simpy3". This allows to update simpy without sudden or
> unexptected breakage of current packages
On 22 May 2015 at 16:06, Tristan Seligmann wrote:
> Or are you saying that the ipaddress backport is not compatible with
> python3 stdlib's ipaddress? (This would be a very unfortunate state of
> affairs, but impossible to imagine)
This should have been "*not* impossible", of course.
--
mithrand
On May 22, 2015 10:06:34 AM EDT, Tristan Seligmann
wrote:
>On 22 May 2015 at 15:43, Donald Stufft wrote:
>> I'm not sure if I was looking at the wrong ipaddr or something but
>the
>> documentation I found was pretty crappy and looking at it I didn't
>see how to
>> actually use ipaddr the same wa
Le 20/05/2015 18:36, dktrkr...@debian.org a écrit :
> your package either build-depends or depends on the python-support
> package, or uses dh_pysupport in debian/rules file.
I have the feeling that that dependency is useless. pycaml doesn't
provide any Python module (it provides an OCaml module t
On 22 May 2015 at 15:43, Donald Stufft wrote:
> I'm not sure if I was looking at the wrong ipaddr or something but the
> documentation I found was pretty crappy and looking at it I didn't see how to
> actually use ipaddr the same way I was using ipaddress in pip. In addition to
> that, the API doe
> On May 21, 2015, at 9:50 PM, Scott Kitterman wrote:
>
> On Friday, May 22, 2015 12:34:02 AM Brian May wrote:
>> On Fri, 22 May 2015 at 07:14 Scott Kitterman wrote:
>>> I was considering the idea of porting things from ipaddr to ipaddress for
>>> python2, but there's a lot more of that then th
ok, my fault, a package was not installed sorry for noise.
Le ven. 22 mai 2015 à 14:15, olivier sallou a
écrit :
> Hi,
> I try to package a software that supports both python 2 and 3 with future.
> future is not yet available in Debian (I've seen an ITP about it), but I'd
> like to start the
Hi,
I try to package a software that supports both python 2 and 3 with future.
future is not yet available in Debian (I've seen an ITP about it), but I'd
like to start the package on my side.
I have an error when using pybuild, it does not find find_packages (from
setuptools). I wonder what is wro
13 matches
Mail list logo
