MySQL, SQLObject, and TG 1.01b problem

[dmm...@gmail.com]

I ran into some problems upgrading on my Windows box, so ended up
reinstalling python, turbogears, docutils, pythonwin and MySQLDB. Now,
when I run any of my existing apps or even the wiki20 tutorial (which
worked under 0.9a8), I get an error complaining about unicode
(TypeError: Decoding Unicode is not supported). I'm not specifically
using unicode, but I see that someone else ran into that problem with
0.9a9.

http://www.mail-archive.com/turbo...@googlegroups.com/msg16825.html

Any suggestions for what to do? Are there people successfully using
1.01 with MySQL and SQLObject? Did I just miss something with my
reinstall? A configuration setting?

Thanks!
Dianne

[Karl Guertin]

On 9/8/06, dianne...@yahoo.com <dmm...@gmail.com> wrote:
> Any suggestions for what to do? Are there people successfully using
> 1.01 with MySQL and SQLObject? Did I just miss something with my
> reinstall? A configuration setting?

This is a hot-off-the-presses sort of fix, but Oleg just (like 5
minutes ago) put SO 0.7.1RC1 on the cheeseshop and mentions that
selects with UnicodeCols have been fixed. Not sure if that resolves
your problem, but it's worth a shot.

[Doug Woos]

So will "easy_install -Uf Sqlobject" do the job?

Doug Woos

[Karl Guertin]

On 9/8/06, Doug Woos <doug...@gmail.com> wrote:
> So will "easy_install -Uf Sqlobject" do the job?

No need for the f, just "easy_install -U SQLObject" case counts.

[Doug Woos]

"SQLObject 0.7.1dev-r1860 is already the active version in easy-install.pth"

This is the version that got installed w/ TG.

Doug

On 9/8/06, Karl Guertin <gray...@gmail.com> wrote:

[Doug Woos]

On 9/8/06, Doug Woos <doug...@gmail.com> wrote:
>
> "SQLObject 0.7.1dev-r1860 is already the active version in easy-install.pth"
>
> This is the version that got installed w/ TG.
>
>
> Doug

Okay- I deleted that version ad installed rc1. I now get the following
error message when running tg-admin sql status:

"pkg_resources.DistributionNotFound:
SQLObject==bugfix,>=0.7.1dev-r1860,<=0.7.99"

Any thoughts?

Thanks,

Doug

[Doug Woos]

So... not thoughts? Can I not use SQLObject 0.7.1rc1 with TG?

[Karl Guertin]

On 9/11/06, Doug Woos <doug...@gmail.com> wrote:
> So... not thoughts? Can I not use SQLObject 0.7.1rc1 with TG?

I know it's possible to hack the TG version requirements, but I don't
know why setuptools is preferring an older dev release rather than a
newer RC release. I was holding off answering this question in hopes
that someone more knowledgable about setuptools could answer your
problem.

[Elvelind Grandin]

Too me it looks like a setuptools bug. We have to bother PJE about it.

--
cheers
elvelind grandin

[Kevin Dangoor]

If those commas are all interpreted as ANDs, that means that it's
specifically looking for something on the bugfix branch, not just
looking based on version numbers. We should fix that.

Kevin

[Eoghan]

I've run up as far as this step too (removing old SQLObject, then
installing 0.7.1rc1) , is there a manual fix to get TurboGears to
recognise this bugfixed SQLObject? Or do I just wait until e.g.
SQLObject 0.7.2 ?

[Fabio Eduardo Thomaz]

On 9/11/06, Doug Woos <doug...@gmail.com> wrote:
> So... not thoughts? Can I not use SQLObject 0.7.1rc1 with TG?

(sorry for my terrible english.. i'm learning.. :) )

I installed the SQLObject 0.7rc1 and modified the "requires" file of TurboGears EGG-INFO.
(I had installed TG with SQLObject 0.7.1dev_r1)

in windows:
python_path\Lib\site-packages\TurboGears-1.0b1-py2.4.egg\EGG-INFO\requires.txt

from:
SQLObject==bugfix,>=0.7.1dev-r1860,<=0.7.99
to:
SQLObject==bugfix,>=0.7.1dev-r1860 ,<=0.7rc1

I'm newby in TurboGears and I don't know if this modification is recommended to do.
But, for Wiki20 tutorial, it works.

Regards,
Fabio Thomaz

[ben.ha...@gmail.com]

I tried this method and was unable to get it to work. I also noticed
that on x64-64 std is now tg in templates. On my machine I'm still
getting an error and I'm looking at mysql and wondering if I shouldn't
change the encoding or just jump ship for sqlobject in the meantime
until this goes away.Surely its going to get fixed this is a huge
problem. I'm still not sure if its not something in my template (I
mean it has to be a clean one without variables works fine) but even a
fix of a malformed header didn't fix it. I'm at 0.7.1rc1 now at least.
Could it not be mysql encoding latin1 would fix the problem or
something?

[stick...@gmail.com]

Was there ever a resolution to this?

It was mentioned in the thread that doing a 'easy_install -U SQLObject'
would bring SO up to a newer version than 0.7.1 may fix this issue, but
whenever i try to run that command it tells me that 0.7.1 is already
the active version..?