Re: Importing by file name

From	Mark Lawrence <breamoreboy@yahoo.co.uk>
Subject	Re: Importing by file name
Date	2013-11-24 16:30 +0000
References	<CAPTjJmqhiyT9zVHFRyKH0UwhdhFgZxA1rcbarChePMyfK7dDTA@mail.gmail.com> <CALwzidmqKkpuugv2zvu-8RpoVZF899G2Hpdmd_kVn8a33WMWFw@mail.gmail.com> <mailman.3119.1385280468.18130.python-list@python.org> <52920a19$0$29993$c3e8da3$5496439d@news.astraweb.com>
Newsgroups	comp.lang.python
Message-ID	<mailman.3143.1385310641.18130.python-list@python.org> (permalink)

Show all headers | View raw

On 24/11/2013 14:15, Steven D'Aprano wrote:
>
> That was the case up to 3.3, but Python 3.4 has the import machinery re-
> written in pure Python (except for a tiny bit of bootstrapping machinery,
> if I understand correctly). I understand that nobody understood the
> import machinery in full (although there were a couple of people who
> understood most of it), and that moving it to Python was a Herculean job.
> If I remember correctly, it uncovered a number of undetected bugs and
> dark corners with unspecified behaviour.
>

The import mechanism was rewritten in 3.3 see 
http://docs.python.org/3/whatsnew/3.3.html#importlib.  PEP 451 also does 
work on the import mechanism http://www.python.org/dev/peps/pep-0451/ 
This is in 3.4, see http://bugs.python.org/issue18864 and a rather long 
list of associated issues.

-- 
Python is the second best programming language in the world.
But the best has yet to be invented.  Christian Tismer

Mark Lawrence

Back to comp.lang.python | Previous | Next — Previous in thread | Find similar | Unroll thread

Thread

Re: Importing by file name Chris Angelico <rosuav@gmail.com> - 2013-11-24 19:07 +1100
  Re: Importing by file name Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2013-11-24 14:15 +0000
    Re: Importing by file name Chris Angelico <rosuav@gmail.com> - 2013-11-25 01:25 +1100
    Re: Importing by file name Mark Lawrence <breamoreboy@yahoo.co.uk> - 2013-11-24 16:30 +0000

csiph-web