Am 18.06.2010 um 22:17 schrieb Gisborne:
On Jun 18, 12:41 pm, "Diez B. Roggisch" <[email protected]> wrote:
You're right; I didn't have the virtualenv activated. But I had it
activated when I installed all this, and with it activated now, and
with SQLAlchemy 0.5.8 installed, I get "ImportError: No module named
dalects.postgresql.base", which I understand is because GeoAlchemy
requires at least SQLAlchemy 0.6.
If that's a literal copy of what is seen on your screen, it's a bug
in
geoalchemy - because "dalects" should be dialects I presume. If not,
please copy and paste real error-messages.
Typo: it was ImportError: No module named dialects.postgresql.base
However, I think you should do this one step at a time - first,
create
a clean venv, and as Brad mentioned py2.6 has issues with the --no-
site-packages directive, I again recommend cleaning the python
installation.
Then, install TG2 into a venv, and see if it works. Then, install
geoalchemy, and see if and what breaks. And frankly, as the
geoalchemy
guys for help ;)
I've been around and around doing all this from scratch several times.
I've been at this for five days. I've tried installing different
versions of various packages, installing by downloading them rather
than using easy_install, and so on. I always wind up stuck at this
point. But I'll try asking on the GeoAlchemy lists. Thanks.
Well, you said you have troubles starting a TG2 project. Is that the
case? Or does adding geoalchemy into the equation make things fail?
Diez
--
You received this message because you are subscribed to the Google Groups
"TurboGears" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/turbogears?hl=en.
