On Sat, 12 Aug 2006 16:57:52 -0600, Bruce Sass <[EMAIL PROTECTED]> said:
> On Sat August 12 2006 09:34, Matthias Klose wrote: First time I've
> seen the design goals laid out like this. Thanks, and sorry if this
> is out of place.
>> No, not the whole design goal. Although the document is titled
>> "developer's view", the other goals should be mentioned as well.
>> These are meant to work around processes in debian which are
>> currently suboptimal, but unlikely to change.
>>
>> - The need to support more than one version of a python runtime or
>> to support different implementations was seen. It takes a while
>> until applications support a new version.
> What is needed now is a way to prevent all but the "default" modules
> and those selected by the admin from being built for all installed
> runtimes so Debian can re-step forward and properly support multiple
> runtimes.
> The new policies all-or-nothing attitude wrt modules is too much. It
> effectively forces one Python only and unnecessarily discourages
> Python hackers and developers because the cost of carrying all
> modules for all installed versions, instead of just those modules
> needed for the work being done in the different versions, can be
> quite high for someone with a comprehensive installation of even one
> Python version.
Have you actually read the draft proposal? How did you come to
the conclusion that only one run time is supported by that?
manoj
--
"Whoever undertakes to set himself up as a judge of Truth and
Knowledge is shipwrecked by the laughter of the gods."-- Albert
Einstein
Manoj Srivastava <[EMAIL PROTECTED]> <http://www.debian.org/%7Esrivasta/>
1024D/BF24424C print 4966 F272 D093 B493 410B 924B 21BA DABB BF24 424C
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
