[Trac] Re: Problems upgrading existing trac projects to trac 0.11
Noah Kantrowitz <
kantrn@...>
2008-01-02 21:23:21 GMT
Python modules are only installed against a single major version. In
the case of modules that include a compiled portion (such as database
bindings) this is enforced by the interpreter because the ABI changes.
You will just need to reinstall the bindings for 2.5 (ps: pyscopg2 is
generally preferred if you have an option). 0.11 continues the Trac
tradition of full compat from 2.3 up, so you can install it under 2.4
if you wish.
--Noah
On Jan 2, 2008, at 1:15 PM, julie.tittler@... wrote:
>
> I have a windows XP server. I've followed the installation
> instructions on the web site for trac 0.11. That seemed to go OK. I'm
> upgrading from 10.4 with Python 24, to trac 0.11 with Python 2.5. When
> I followed the instructions for upgrading a trac project with trac-
> admin, I get an error about pyPgSQL, as listed below. Now then, I do
> still have it installed but pyPgSQL 2.4, which was the version to go
> with Python 2.4. On their website, there doesn't seem to be one for
> Python 2.5 under the windows releases. Is this true? Will the PyPgSQL
> for 2.4 work with 2.5? If not, can 0.11 work with Python 2.4 and
> PyPgSQL for 2.4?
>
> Traceback (most recent call last):
> File "C:\Python25\Scripts\trac-admin-script.py", line 8, in <module>
> load_entry_point('trac==0.11b1', 'console_scripts', 'trac-admin')
> ()
> File "c:\python25\lib\site-packages\trac-0.11b1-py2.5.egg\trac\admin
> \console.py", line 1194, in run
> return admin.onecmd(command)
> File "c:\python25\lib\site-packages\trac-0.11b1-py2.5.egg\trac\admin
> \console.py", line 102, in onecmd
> rv = cmd.Cmd.onecmd(self, line) or 0
> File "c:\Python25\lib\cmd.py", line 219, in onecmd
> return func(arg)
> File "c:\python25\lib\site-packages\trac-0.11b1-py2.5.egg\trac\admin
> \console.py", line 1098, in do_upgrade
> self.db_open()
> File "c:\python25\lib\site-packages\trac-0.11b1-py2.5.egg\trac\admin
> \console.py", line 149, in db_open
> return self.env_open().get_db_cnx()
> File "c:\python25\lib\site-packages\trac-0.11b1-py2.5.egg\trac
> \env.py", line 250, in get_db_cnx
> return DatabaseManager(self).get_connection()
> File "c:\python25\lib\site-packages\trac-0.11b1-py2.5.egg\trac\db
> \api.py", line 76, in get_connection
> return self._cnx_pool.get_cnx(self.timeout or None)
> File "c:\python25\lib\site-packages\trac-0.11b1-py2.5.egg\trac\db
> \pool.py", line 101, in get_cnx
> cnx = self._connector.get_connection(**self._kwargs)
> File "c:\python25\lib\site-packages\trac-0.11b1-py2.5.egg\trac\db
> \postgres_backend.py", line 46, in get_connection
> cnx = PostgreSQLConnection(path, user, password, host, port,
> params)
> File "c:\python25\lib\site-packages\trac-0.11b1-py2.5.egg\trac\db
> \postgres_backend.py", line 117, in __init__
> from pyPgSQL import PgSQL
> ImportError: No module named pyPgSQL
>
> Thanks,
> Julie
> >
>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Trac Users" group.
To post to this group, send email to trac-users@...
To unsubscribe from this group, send email to trac-users-unsubscribe@...
For more options, visit this group at http://groups.google.com/group/trac-users?hl=en
-~----------~----~----~----~------~----~------~--~---