On Sun, Sep 01, 2013 at 03:31:45PM +0200, Ludovic Courtès wrote:
> When ‘native-search-paths’ changes in python3, it’s not python3 that
> behaves differently: it’s the build process of packages using it that
> does.
Not really. Then the output of, say, pytz, will change when the
native-search-path
Andreas Enge skribis:
> On Sat, Aug 31, 2013 at 08:06:34PM +0200, Ludovic Courtès wrote:
>> It has no effect in the build of Python itself; its effect is only when
>> building Python code that uses Python and one or more Python libs.
>
> I still think something is wrong here and that this variabl
On Sat, Aug 31, 2013 at 08:06:34PM +0200, Ludovic Courtès wrote:
> It has no effect in the build of Python itself; its effect is only when
> building Python code that uses Python and one or more Python libs.
I still think something is wrong here and that this variable should be
included into the c
Andreas Enge skribis:
> On Sat, Aug 31, 2013 at 06:07:35PM +0200, Ludovic Courtès wrote:
>> Andreas Enge skribis:
>> > I just noticed that there is a variable native-search-paths in python-2,
>> > which looks like it should be updated for python 3. However, when I modify
>> > the package accordi
On Sat, Aug 31, 2013 at 06:07:35PM +0200, Ludovic Courtès wrote:
> Andreas Enge skribis:
> > I just noticed that there is a variable native-search-paths in python-2,
> > which looks like it should be updated for python 3. However, when I modify
> > the package accordingly, it is not recompiled. Ho
Andreas Enge skribis:
> I just noticed that there is a variable native-search-paths in python-2,
> which looks like it should be updated for python 3. However, when I modify
> the package accordingly, it is not recompiled. How come? Is this variable
> really needed?
Yes it is [0]. :-)
Changing
I just noticed that there is a variable native-search-paths in python-2,
which looks like it should be updated for python 3. However, when I modify
the package accordingly, it is not recompiled. How come? Is this variable
really needed?
Andreas
