[Import-sig] versions? (was: Kick-off)
Sat, 5 Feb 2000 04:06:36 -0800 (PST)
How about we just start blazing a path. If we get it done before 1.6.0,
then we'll be happy. I don't see a particular reason to partition the
releases *before* we even know where we're going, what we'll build, and
how long it may take to complete that. In other words, let's ignore the
versions -- that's putting the cart before the horse.
I read Gordon's opening note as a way to focus attention. We start with
the short-term, finish that, then move onto the long-term.
On Fri, 4 Feb 2000, Fredrik Lundh wrote:
> Gordon wrote:
> > Short-term: Provide a "new architecture import hooks" module
> > for the standard library. This would deprecate ihooks and
> > friends, and provide developers with a way of learning the new
> > architecture.
> 1.6.1 <= version <= 1.7, right?
> > Long-term: Reform the entire import architecture of Python.
> > This affects Python start-up, the semantics of sys.path, and
> > the C API to importing.
> 1.7 <= version < 3000, right?
> > The model for this is, of course, Greg's imputil.py (Greg, your
> > latest version is not yet on your website which still has a
> > November version).
> I'd like to add an ultra-short-term issue: possible changes
> to 1.6.0 that makes it easier to experiment with alternate
> import strategies, mostly for installation tools like gordon's
> install and pythonworks' deployment subsystem.
> (as discussed on last week's consortium meeting)
> most importantly, I'd like to come up with a way to execute
> small snippets of script code *before* Python attempts to
> import stuff like exceptions.py.
> Import-sig mailing list
Greg Stein, http://www.lyra.org/