Re: [Q] ImportError by __import__() on Python >= 3.4

2016-06-09 Thread Makoto Kuwata
On Wed, Jun 8, 2016 at 10:24 PM, Michael Selik wrote: > By the way, why choose to write, import, and delete modules? I'd think > exec'ing code would be sufficient. > > In order to test my own framework for web application. It loads controller classes lazily. In other words, it loads python module

Re: [Q] ImportError by __import__() on Python >= 3.4

2016-06-08 Thread Michael Selik
By the way, why choose to write, import, and delete modules? I'd think exec'ing code would be sufficient. On Wed, Jun 8, 2016, 5:52 AM Makoto Kuwata wrote: > On Tue, Jun 7, 2016 at 7:28 AM, Michael Selik > wrote: > >> On Thu, Jun 2, 2016 at 10:06 AM Makoto Kuwata wrote: >> >>> I have a trouble

Re: [Q] ImportError by __import__() on Python >= 3.4

2016-06-08 Thread Makoto Kuwata
On Tue, Jun 7, 2016 at 7:28 AM, Michael Selik wrote: > On Thu, Jun 2, 2016 at 10:06 AM Makoto Kuwata wrote: > >> I have a trouble around __import__(). >> > > The docs for __import__ strongly recommend that you use importlib instead > https://docs.python.org/3.5/library/importlib.html#importlib.i

Re: [Q] ImportError by __import__() on Python >= 3.4

2016-06-06 Thread Michael Selik
On Thu, Jun 2, 2016 at 10:06 AM Makoto Kuwata wrote: > I have a trouble around __import__(). > The docs for __import__ strongly recommend that you use importlib instead https://docs.python.org/3.5/library/importlib.html#importlib.import_module The docs for ``importlib.import_module`` suggest th

Re: [Q] ImportError by __import__() on Python >= 3.4

2016-06-04 Thread Makoto Kuwata
On Sat, Jun 4, 2016 at 3:15 AM, MRAB wrote: > On 2016-06-03 06:48, Makoto Kuwata wrote: > > On Fri, Jun 3, 2016 at 9:31 AM, MRAB > pyt...@mrabarnett.plus.com>> wrote: >> >> On 2016-06-02 15:04, Makoto Kuwata wrote: >> >> Hi, >> >> I have a trouble around __import__(). >>

Re: [Q] ImportError by __import__() on Python >= 3.4

2016-06-03 Thread MRAB
On 2016-06-03 06:48, Makoto Kuwata wrote: On Fri, Jun 3, 2016 at 9:31 AM, MRAB > wrote: On 2016-06-02 15:04, Makoto Kuwata wrote: Hi, I have a trouble around __import__(). The following sample code works well on Python <= 3.3,

Re: [Q] ImportError by __import__() on Python >= 3.4

2016-06-02 Thread MRAB
On 2016-06-02 15:04, Makoto Kuwata wrote: Hi, I have a trouble around __import__(). The following sample code works well on Python <= 3.3, but it raises ImportError on Python >= 3.4. ## importtest.py import sys, os, shutil def test(name): try: ## create 'foo/__

Re: [Q] ImportError by __import__() on Python >= 3.4

2016-06-02 Thread Makoto Kuwata
On Thu, Jun 2, 2016 at 11:15 PM, Michael Selik wrote: > > > On Thu, Jun 2, 2016 at 10:06 AM Makoto Kuwata wrote: > >> os.mkdir(name) >> with open(name + "/__init__.py", 'w') as f: >> f.write("X=1") >> f.flush() >> >> Please give me any advi

Re: [Q] ImportError by __import__() on Python >= 3.4

2016-06-02 Thread Michael Selik
On Thu, Jun 2, 2016 at 10:06 AM Makoto Kuwata wrote: > os.mkdir(name) > with open(name + "/__init__.py", 'w') as f: > f.write("X=1") > f.flush() > > Please give me any advices or hints. > This wasn't your question, but you don't need to flu

[Q] ImportError by __import__() on Python >= 3.4

2016-06-02 Thread Makoto Kuwata
Hi, I have a trouble around __import__(). The following sample code works well on Python <= 3.3, but it raises ImportError on Python >= 3.4. ## importtest.py import sys, os, shutil def test(name): try: ## create 'foo/__init__.py' file os.mkdir(name)