Hello, thanks for your reply
> you can
> 1) invoke dh twice with different set of options (if these modules
>are in two different directories or use two different setup.py
>files/options)
the use the same setup.py for now...
> or
> 2) (ab)use --ext-dest-dir/--ext-pattern to move some fil
On Jul 20, 2015, at 01:12 PM, Dimitri John Ledkov wrote:
>Would it be fair to have a goal to only have PEP420 style namespaces
>in python3 world?
I think so, yes. Since we're integrators, I think it's fine for us to make
this decision, and deal with any fallout that might occur, though I think t
On 20 July 2015 at 13:04, Julien Cristau wrote:
> On Mon, Jul 20, 2015 at 07:58:13 -0400, Barry Warsaw wrote:
>
>> On Jul 20, 2015, at 01:12 PM, Julien Cristau wrote:
>>
>> >Is that a serious question? Why should debian-python, for no good
>> >reason, break things that work just fine?
>>
>> Becau
[PICCA Frederic-Emmanuel, 2015-07-17]
> I am working on a source package pymca, which will provide 2 modules
> PyMca5 and fisx
[...]
> export PYBUILD_NAME=pymca5
> %:
> dh $@ --with python2,python3 --buildsystem=pybuild
you can
1) invoke dh twice with different set of options (if these mo
On Mon, Jul 20, 2015 at 07:58:13 -0400, Barry Warsaw wrote:
> On Jul 20, 2015, at 01:12 PM, Julien Cristau wrote:
>
> >Is that a serious question? Why should debian-python, for no good
> >reason, break things that work just fine?
>
> Because it doesn't really work well when you are supporting b
On Jul 20, 2015, at 01:12 PM, Julien Cristau wrote:
>Is that a serious question? Why should debian-python, for no good
>reason, break things that work just fine?
Because it doesn't really work well when you are supporting both Python 2 and
Python 3. For example, if you have the 'foo' namespace
On Mon, Jul 20, 2015 at 13:12:14 +0200, Julien Cristau wrote:
> On Mon, Jul 20, 2015 at 11:58:07 +0100, Dimitri John Ledkov wrote:
>
> > On 20 July 2015 at 09:00, Julien Cristau wrote:
> > > On Mon, Jul 20, 2015 at 09:56:55 +0200, Piotr Ożarowski wrote:
> > >
> > >> [Julien Cristau, 2015-07-20]
On Mon, Jul 20, 2015 at 11:58:07 +0100, Dimitri John Ledkov wrote:
> On 20 July 2015 at 09:00, Julien Cristau wrote:
> > On Mon, Jul 20, 2015 at 09:56:55 +0200, Piotr Ożarowski wrote:
> >
> >> [Julien Cristau, 2015-07-20]
> >> > On Sun, Jul 19, 2015 at 21:28:32 +0200, Piotr Ożarowski wrote:
> >>
On 20 July 2015 at 09:00, Julien Cristau wrote:
> On Mon, Jul 20, 2015 at 09:56:55 +0200, Piotr Ożarowski wrote:
>
>> [Julien Cristau, 2015-07-20]
>> > On Sun, Jul 19, 2015 at 21:28:32 +0200, Piotr Ożarowski wrote:
>> >
>> > > Should we patch distutils/setuptools to not generate them? It generates
On Mon, Jul 20, 2015 at 09:56:55 +0200, Piotr Ożarowski wrote:
> [Julien Cristau, 2015-07-20]
> > On Sun, Jul 19, 2015 at 21:28:32 +0200, Piotr Ożarowski wrote:
> >
> > > Should we patch distutils/setuptools to not generate them? It generates
> > > them even for Python 3.X (which has PEP420 imple
[Julien Cristau, 2015-07-20]
> On Sun, Jul 19, 2015 at 21:28:32 +0200, Piotr Ożarowski wrote:
>
> > Should we patch distutils/setuptools to not generate them? It generates
> > them even for Python 3.X (which has PEP420 implemented)
>
> Please don't. Using an pkg_resources-style vs PEP420 namespa
On Sun, Jul 19, 2015 at 21:28:32 +0200, Piotr Ożarowski wrote:
> Should we patch distutils/setuptools to not generate them? It generates
> them even for Python 3.X (which has PEP420 implemented)
Please don't. Using an pkg_resources-style vs PEP420 namespace should
be an upstream decision made in
12 matches
Mail list logo
