On Wednesday, April 24, 2013 3:08:27 PM UTC-4, Neil Cerutti wrote:
> On 2013-04-24, Forafo San <ppv.g...@gmail.com> wrote:
>
> > Hello All,
>
> > I'm running Python version 2.7.3_6 on a FreeBSD system. The following
> > session in a Python interpreter throws a mysterious TypeError:
>
> >
>
> > ------------------------------------------
>
> > [ppvora@snowfall ~/xbrl]$ python
>
> > Python 2.7.3 (default, Apr 22 2013, 18:42:18)
>
> > [GCC 4.2.1 20070719 [FreeBSD]] on freebsd8
>
> > Type "help", "copyright", "credits" or "license" for more information.
>
> >>>> import glob
>
> > Traceback (most recent call last):
>
> > File "<stdin>", line 1, in <module>
>
> > File "glob.py", line 14, in <module>
>
> > myl = glob.glob('data/*.xml')
>
> > TypeError: 'module' object is not callable
>
> > ------------------------------------------
>
> > The file glob.py that the error refers to was run under another
>
> > screen session. It's a mystery why even that program threw an
>
> > error. Regardless, why should that session throw an import
>
> > error in this session? Weird. Any help is appreciated. Thanks,
>
>
>
> 'Cause Python's import statement looks in the current directory
>
> first for files to import. So you're importing your own
>
> error-riddled and mortal glob.py, rather than Python's pristine
>
> and Olympian glob.py.
>
>
>
> --
>
> Neil Cerutti
>
> "This room is an illusion and is a trap devisut by Satan. Go
>
> ahead and dauntlessly! Make rapid progres!"
>
> --Ghosts 'n Goblins
OK, lesson learned: Take care not to have module names that conflict with
python's built ins. Sorry for being so obtuse.
--
http://mail.python.org/mailman/listinfo/python-list
