Nick Coghlan wrote:
> Rationalise *.pkg and *.pth files
> -
> [...]
>
> Use an interpreter configuration file?
> --
When dealing with these issues, please consider also startup time. Python is
already "pretty slow" at startup, an
> [1] http://www.jython.org/docs/registry.html
>
On the new Jython website the same content is here:
http://www.jython.org/Project/userguide.html#the-jython-registry
Though I don't think there are any changes to this content.
-Frank
___
Python-3000 mai
A couple I accidentally left off my original list:
Rationalise *.pkg and *.pth files
-
site.py processes *.pth files in the site-packages directory (the exact
location being platform dependent) and adds things to sys.path as per the
documentation of the site modu
Ka-Ping Yee <[EMAIL PROTECTED]> wrote:
>
> On Sun, 16 Jul 2006, Nick Coghlan wrote:
> > Taking the "import system" to be the overall interaction between the
> > Python module namespace and the file system of the underlying computer,
> > I thought I'd start compiling a list of the questions we'll
On Sun, 16 Jul 2006, Nick Coghlan wrote:
> Taking the "import system" to be the overall interaction between the
> Python module namespace and the file system of the underlying computer,
> I thought I'd start compiling a list of the questions we'll want to
> consider for Py3k.
I'd like to add "relo
On 7/15/06, Nick Coghlan <[EMAIL PROTECTED]> wrote:
Taking the "import system" to be the overall interaction between the Pythonmodule namespace and the file system of the underlying computer, I thought I'dstart compiling a list of the questions we'll want to consider for Py3k. The
answers to some o
Taking the "import system" to be the overall interaction between the Python
module namespace and the file system of the underlying computer, I thought I'd
start compiling a list of the questions we'll want to consider for Py3k. The
answers to some of them may be "the status quo is fine" but we s
