Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.python > #60374

Re: Importing by file name

Show all headers | View raw

On Mon, Nov 25, 2013 at 1:15 AM, Steven D'Aprano
<steve+comp.lang.python@pearwood.info> wrote:
> On Sun, 24 Nov 2013 19:07:38 +1100, Chris Angelico wrote:
>
>> I know the recent Pythons give a lot of import power to the script. But
>> maybe I'm just asking too much, and some of this stuff really is magical
>> and implemented in C?
>
> 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.

Alright, I'll sit tight for 3.4 beta then... or maybe play with what's
currently in trunk (which is my 'python3' executable on Sikorsky). I
haven't seen anything that lets me replace the master in that way, but
there is a HUGE amount of Python's bootstrap that I have never even
peeked into.

ChrisA

Back to comp.lang.python | Previous | Next — Previous in thread | Next 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