Re: The impact of multiarch on upstream Python

2011-05-03 Thread Colin Watson
On Thu, Apr 21, 2011 at 10:10:04PM -0400, Barry Warsaw wrote: > On Apr 20, 2011, at 10:19 PM, Matthias Klose wrote: > >> * Consideration for backward compatibility so that Python's build would > >>continue to work without change. > > > >that (having symlinks for the files in the old locations)

Re: The impact of multiarch on upstream Python

2011-04-22 Thread Barry Warsaw
On Apr 20, 2011, at 10:19 PM, Matthias Klose wrote: >Python upstream, and many other upstream packages shouldn't need to search >for headers and libraries in the standard path of the compiler. It's done >very often, but the right thing is to use the compiler's idea of the search >paths and not to

Re: The impact of multiarch on upstream Python

2011-04-20 Thread Matthias Klose
On 04/20/2011 08:41 PM, Barry Warsaw wrote: When multiarch landed in Natty, it caused some problems with upstream Python. With my Python core developer hat on, I wanted to relate my experiences in dealing with that change. I do this purely in the spirit of improving things for the next time. I'

The impact of multiarch on upstream Python

2011-04-20 Thread Barry Warsaw
When multiarch landed in Natty, it caused some problems with upstream Python. With my Python core developer hat on, I wanted to relate my experiences in dealing with that change. I do this purely in the spirit of improving things for the next time. I'm not pointing any fingers or casting any blam