Hello all,
I'm running FreeBSD 8.2-RELEASE. I am attempting to do some really simple things in Python (python27-2.7.3_6) which results in weird behavior. I'm reaching out to the FreeBSD forums instead of Python groups because I think this may be a FreeBSD related issue. For example:
The error above refers to a Python program glob.py that I had run in a different screen session. The program itself doesn't appear to have any errors, but throws that TypeError. (This is also a mystery). But why would something that threw an error under a different screen session screw up something in another session?
Any help is highly appreciated.
-Premal
I'm running FreeBSD 8.2-RELEASE. I am attempting to do some really simple things in Python (python27-2.7.3_6) which results in weird behavior. I'm reaching out to the FreeBSD forums instead of Python groups because I think this may be a FreeBSD related issue. For example:
Code:
[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 error above refers to a Python program glob.py that I had run in a different screen session. The program itself doesn't appear to have any errors, but throws that TypeError. (This is also a mystery). But why would something that threw an error under a different screen session screw up something in another session?
Any help is highly appreciated.
-Premal