Re: A thread import problem

From	Dennis Lee Bieber <wlfraed@ix.netcom.com>
Subject	Re: A thread import problem
Date	2012-07-24 00:43 -0400
Organization	> Bestiaria Support Staff <
References	(2 earlier) <2u8m085co3j3n97jorkl04o5hr1orqb7la@invalid.netcom.com> <CA+WuaSde=GntxGMVTScOUw4_a+jqQS+nme0VpZVgH_219Qo9jA@mail.gmail.com> <5gfm08htgbrum782hfv5fqkb4084qra7vq@invalid.netcom.com> <CA+WuaScB1jycdBNPosEePGUX=8n80Wst3tGv672TK2FVq-KAig@mail.gmail.com> <CA+WuaSdMnWE6sr63Twd+VJ_YMpkrbZ1qaVwXZ4RCL77JQuLPMw@mail.gmail.com>
Newsgroups	comp.lang.python
Message-ID	<mailman.2517.1343104995.4697.python-list@python.org> (permalink)

Show all headers | View raw

	Sounds like someone had the time to actually work out the
parser/editor scheme I implied earlier.

	My focus had been on adjusting the programs to be usable under an
import scheme by ensuring they don't try to "run" logic during the
import -- deferring that to a post-import phase.

	The description you gave is of scanning the program to
extract/execute the imports first, followed by executing the "remains"
(the logic that was causing the problem when imported).


-- 
	Wulfraed                 Dennis Lee Bieber         AF6VN
        wlfraed@ix.netcom.com    HTTP://wlfraed.home.netcom.com/

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

Thread

Re: A thread import problem Dennis Lee Bieber <wlfraed@ix.netcom.com> - 2012-07-24 00:43 -0400

csiph-web