package questions
Daniel
daniel.watrous at gmail.com
Fri May 22 18:10:41 EDT 2009
On May 22, 3:37 pm, Scott David Daniels <Scott.Dani... at Acm.Org> wrote:
> Daniel wrote:
> > I'm on WinXP using Python 2.5 Sorry I didn't mention that at first.
>
> Generally, you want the full version number (my 2.5 is 2.5.4).
> However, I set up your demo setup, and found that 2.6.2 worked, and
> 2.5.4 failed in the same way you see. I also see that even inside
> the effects directory (with 2.6), I can use the syntax to work.
> However, 2.5 is nearing "security fixes only" status, so I'd try
> moving to 2.6. In the following, "C:\...\Py" is in my standard path.
>
> C:\...\Py\sound\effects> \python26\python -m sound.effects.surround
> effects package imported
> surround started
> echo imported
> echo in
> formats package imported
> formats in
> filters package imported
> equalizer imported
> filters in
>
> But if I make a file:
> C:\...\Py\> type demo_sound.py
> import sound.effects.surround
> print('all loaded')
> I can then:
> C:\...\Py> \python25\python demo_sound.py
> effects package imported
> surround started
> echo imported
> echo in
> formats package imported
> formats in
> filters package imported
> equalizer imported
> filters in
> all loaded
> or even:
> C:\...\Py\sound\effects> \python25\python demo_sound.py
> effects package imported
> surround started
> echo imported
> echo in
> formats package imported
> formats in
> filters package imported
> equalizer imported
> filters in
> all loaded
>
> So, not what you want to hear, but at least identified. I expect
> nobody wants to crawl into that code to make your case work,
> especially since you can switch to 2.6 and have it work. The
> import code is said to be quite nasty and being rewritten/redocumented.
>
> --Scott David Daniels
> Scott.Dani... at Acm.Org
Thanks for doing the experiment. I'll begin to consider testing with
python 2.6 for a possible upgrade.
Daniel
More information about the Python-list
mailing list