Can't see any potential conflicts. I have the problem for both
track_changes(True) and track_changes(False). When I import from shell:
[aicbt@web331 web2py2.2.1]$ python web2py.py -S init
web2py Web Framework
Created by Massimo Di Pierro, Copyright 2007-2012
Version 2.2.1 (2012-10-21 16:57:04) stable
Database drivers available: SQLite(sqlite3), MySQL(pymysql),
MySQL(MySQLdb), PostgreSQL(psycopg2), PostgreSQL(pg8000), IMAP(imaplib)
WARNING:web2py:import IPython error; use default python shell
Python 2.7.3 (default, May 18 2012, 14:51:16)
[GCC 4.4.6 20110731 (Red Hat 4.4.6-3)] on linux2
Type "help", "copyright", "credits" or "license" for more information.
(InteractiveConsole)
>>> import matplotlib.pylab
Traceback (most recent call last):
File "<console>", line 1, in <module>
File
"/home/aicbt/webapps/alternate_config/web2py2.2.1/gluon/custom_import.py",
line 77, in custom_importer
raise ImportError, 'Cannot import module %s' % str(e)
ImportError: Cannot import module 'matplotlib'
This shell command works with web2py version 2.1. Also, "import matplotlib"
(without the pylab) works fine for 2.2.1.
On Friday, November 2, 2012 1:22:03 PM UTC, Massimo Di Pierro wrote:
>
> Do you have anything in your app/modules/* that may conflict? Did you set
> track_changes(True) or not? If you do web2py.py -S yourapp can you import
> form the web2py shell?
>
> On Friday, 2 November 2012 02:18:47 UTC-5, Neil wrote:
>>
>> A little more info:
>>
>> - On linux (works fine on Windows)
>> - matplotlib is an egg in the lib directory
>> - "import matplotlib" works, but "import matplotlib.pylab" doesn't
>> - Has worked fine in every version up to 2.1
>>
>> Any ideas for a workaround or to debug further?
>>
>> On Thursday, November 1, 2012 9:52:57 PM UTC, Massimo Di Pierro wrote:
>>>
>>> Where is matplotlib installed?
>>>
>>> On Thursday, 1 November 2012 15:51:14 UTC-5, Neil wrote:
>>>>
>>>> I just upgraded from 2.1 to 2.2.1, and I can no longer import
>>>> matplotlib. I get the following error:
>>>>
>>>> ImportError: Cannot import module 'matplotlib'
>>>>
>>>>
>>>> Is this related to the custom import? Perhaps it is the same as issue 1125?
>>>>
>>>>
--
