When trying to package python3-pipeline (see http://bugs.debian.org/753556),
I encountered a problem with the python3 dependencies:
dh_python3 -O--buildsystem=pybuild
I: dh_python3 pydist:181: Cannot find installed package that provides
futures. Using python3-futures as package name. Please add "f
* Barry Warsaw: " Re: Packaging of suds-jurko (was: suds)" (Wed, 2 Jul 2014
11:00:34 -0400):
> On Jul 02, 2014, at 04:16 PM, Mathias Behrle wrote:
>
> >>* I still have not taken over the original project's documentation
> >> and that is something I'd really like to do so I can update it wi
* Jurko Gospodnetić: " Re: Packaging of suds-jurko" (Wed, 02 Jul 2014 20:14:33
+0200):
>Hi Mathias.
>
> On 1.7.2014. 13:10, Mathias Behrle wrote:
> > The first tests on suds-jurko are looking very promising. I built the
> > package succesfully as a drop-in replacement for the current python
Hi Mathias.
On 1.7.2014. 13:10, Mathias Behrle wrote:
The first tests on suds-jurko are looking very promising. I built the
package succesfully as a drop-in replacement for the current python-suds
package. It builds correctly for python2 and python3 with all tests. I tested
part of the functio
On Jul 02, 2014, at 05:19 PM, Jurko Gospodnetić wrote:
>Do debian distributions still actually package `distribute` instead of
>`setuptools`?
Not in sid/unstable/jessie (unreleased), but yes in wheezy. I'll update that
page.
-Barry
--
To UNSUBSCRIBE, email to debian-python-requ...@lists.debia
I hope not, it’s way behind setuptools at this point.
On Jul 2, 2014, at 11:19 AM, Jurko Gospodnetić wrote:
> Hi all.
>
> Just wandering if the information from https://wiki.debian.org/Python about
> 'Deviations from upstream' up to date. Not a Debian user myself, but the
> following notes
Hi all.
Just wandering if the information from https://wiki.debian.org/Python
about 'Deviations from upstream' up to date. Not a Debian user myself,
but the following notes seem weird:
The python-setuptools package installs the Distribute fork instead
of the standard setuptools.
The pyt
On Jul 02, 2014, at 04:16 PM, Mathias Behrle wrote:
>>* I still have not taken over the original project's documentation
>> and that is something I'd really like to do so I can update it with all
>> the fixes/updates made to the library. If anyone has experience with
>> epydocs and the tool
* Jurko Gospodnetić: " Re: Re: Packaging of suds-jurko (was: suds)" (Wed, 02
Jul 2014 12:15:35 +0200):
Hi Jurko,
[...]
>* I still have not taken over the original project's documentation
> and that is something I'd really like to do so I can update it with all
> the fixes/updates made to
On Jul 2, 2014, at 5:09 AM, Mathias Behrle wrote:
>> *Puts on PyPI Admin Hat*
>>
>> Probably if suds-jurko or whatever is the unofficial “suds” that people
>> should
>> be using then there is a good chance that PyPI would be willing to transfer
>> the name of suds to one of the forks. I’d have
Hi all.
Probably if suds-jurko or whatever is the unofficial “suds” that
people should be using then there is a good chance that PyPI
would be willing to transfer the name of suds to one of the
forks. I’d have to talk to Richard to be sure about that but
it’s potentially an option.
That inde
* Donald Stufft: " Re: Packaging of suds-jurko (was: suds)" (Tue, 1 Jul 2014
17:55:17 -0400):
>
> On Jul 1, 2014, at 5:41 PM, Barry Warsaw wrote:
>
> > On Jul 01, 2014, at 01:10 PM, Mathias Behrle wrote:
> >
> >> The first tests on suds-jurko are looking very promising. I built the
> >> pack
* Barry Warsaw: " Re: Packaging of suds-jurko (was: suds)" (Tue, 1 Jul 2014
17:41:28 -0400):
> On Jul 01, 2014, at 01:10 PM, Mathias Behrle wrote:
>
> >The first tests on suds-jurko are looking very promising. I built the package
> >succesfully as a drop-in replacement for the current python-su
13 matches
Mail list logo
