On 9/14/07, "Martin v. Löwis" <[EMAIL PROTECTED]> wrote:
> The best way would be to not use import, but provide a separate
> function (e.g. calling it "require").
>
yepp, that's probably the cleanest and quickest solution. i needed
to see all the alternatives to realize this though. sorry.
--
> so i'm wondering, is there a quick way to just add another extension
> to import mechanism? or do i have to write a fully fledged import
> hook?
[this question is off-topic for python-dev]
If recompiling Python is an option, the quick way is to edit the
interpreter, and add that extension.
If
I think you're looking for a PEP 302 style meta hook.
On 9/14/07, tomer filiba <[EMAIL PROTECTED]> wrote:
> a quick question: i'm working on a pythonic build system, where the
> build
> scripts are plain python files. but i want to differentiate them from
> normal
> python files (.py) by a differe
a quick question: i'm working on a pythonic build system, where the
build
scripts are plain python files. but i want to differentiate them from
normal
python files (.py) by a different suffix (say .pyy), but then i can't
import
them.
so i'm wondering, is there a quick way to just add another exten
