Scott Kitterman ha scritto:
> doko uploaded the new policy in python-defaults, so we can consider this
> edition complete. Certainly it's not perfect and I'll be keeping an eye on
> bug submissions.
>
> I've also been added to uploaders for python-defaults and will continue to
> work on this.
On Mon, Dec 14, 2009 at 06:19, Scott Kitterman wrote:
> I know a lot of effort has been made to get the archive ready for Python 2.6.
> Either before or with the Python 2.6 upload, we are going to have to drop
> Python 2.4 as a supported Python version. Any work that could be done now to
> ease t
doko uploaded the new policy in python-defaults, so we can consider this
edition complete. Certainly it's not perfect and I'll be keeping an eye on
bug submissions.
I've also been added to uploaders for python-defaults and will continue to
work on this.
I know a lot of effort has been made to
On su, 2003-08-24 at 08:38, Joe Wreschnig wrote:
> On Sat, 2003-08-23 at 23:54, Donovan Baarda wrote:
> > The problem is, run pydance as any user with write permissions to
> > /usr/share/games/pydance, and the *.py's there will be compiled and
> > saved as *.pyc's using whatever version of python w
On Sat, 2003-08-23 at 23:54, Donovan Baarda wrote:
> On Sun, 2003-08-24 at 09:38, Joe Wreschnig wrote:
> [...]
> > pydance comes with a number of "modules", which are actually its core
> > source code split into managable files. It installs these to
> > /usr/share/games/pydance, and doesn't byte co
On Sun, 2003-08-24 at 09:38, Joe Wreschnig wrote:
[...]
> pydance comes with a number of "modules", which are actually its core
> source code split into managable files. It installs these to
> /usr/share/games/pydance, and doesn't byte compile these. Based on my
> reading of this section, this is n
On Wed, 2003-08-20 at 07:09, Josselin Mouette wrote:
> In order to make it up to date, and to match current packaging
> practices, I have prepared a draft for a python policy update.
> It is available at: http://people.debian.org/~joss/python/
>
> It includes clarifications, a
Le ven 22/08/2003 à 04:37, Donovan Baarda a écrit :
> On Fri, 2003-08-22 at 05:05, Josselin Mouette wrote:
> > Le jeu 21/08/2003 à 04:24, Donovan Baarda a écrit :
> > > --- 1.4 Module Path, a question;
> > >
> > > Do we really want /usr/local/ on the python path before /usr/lib/? This
> > > make
On Fri, 2003-08-22 at 08:02, Josselin Mouette wrote:
> Le mer 20/08/2003 à 14:09, Josselin Mouette a écrit :
> > In order to make it up to date, and to match current packaging
> > practices, I have prepared a draft for a python policy update.
> > It is available at: http://pe
On Fri, 2003-08-22 at 05:05, Josselin Mouette wrote:
> Le jeu 21/08/2003 à 04:24, Donovan Baarda a écrit :
> > --- 1.4 Module Path, a question;
> >
> > Do we really want /usr/local/ on the python path before /usr/lib/? This
> > makes us vulnerable to busted local installs of python modules, in the
Le mer 20/08/2003 à 14:09, Josselin Mouette a écrit :
> In order to make it up to date, and to match current packaging
> practices, I have prepared a draft for a python policy update.
> It is available at: http://people.debian.org/~joss/python/
I have updated this draft using suggest
Le jeu 21/08/2003 à 04:24, Donovan Baarda a écrit :
> --- 1.4 Module Path, a question;
>
> Do we really want /usr/local/ on the python path before /usr/lib/? This
> makes us vulnerable to busted local installs of python modules, in the
> same way that "#!/usr/bin/env python" makes us vulnerable to
On Wed, 2003-08-20 at 22:09, Josselin Mouette wrote:
> In order to make it up to date, and to match current packaging
> practices, I have prepared a draft for a python policy update.
> It is available at: http://people.debian.org/~joss/python/
>
> It includes clarifications, a
Josselin Mouette <[EMAIL PROTECTED]> writes:
> In order to make it up to date, and to match current packaging
> practices, I have prepared a draft for a python policy update.
> It is available at: http://people.debian.org/~joss/python/
>
> It includes clarificati
On Wed, Aug 20, 2003 at 02:09:48PM +0200, Josselin Mouette wrote:
| In order to make it up to date, and to match current packaging
| practices, I have prepared a draft for a python policy update.
| It is available at: http://people.debian.org/~joss/python/
|
| It includes clarifications, a new
In order to make it up to date, and to match current packaging
practices, I have prepared a draft for a python policy update.
It is available at: http://people.debian.org/~joss/python/
It includes clarifications, a new section on bytecompilation, treats the
case of private modules, and appendix B
16 matches
Mail list logo
