Kevin Dangoor wrote: > On 12/29/05, .M. <[EMAIL PROTECTED]> wrote: > > It's not clear from that page whether these two lines are required to > > work off svn. > > > > easy_install -f http://peak.telecommunity.com/snapshots/ RuleDispatch > > Yes, you do need to have RuleDispatch to use 0.9 code. > > > By "developing on Turbogears itself" I initially assumed you meant work > > on the TG codebase as opposed to work on a pre-release version. Can you > > clarify? > > When I wrote that doc, I assumed that the primary use case for getting > the svn version was to work on TurboGears itself. Of course, with > 0.9's batch of goodies, there are lots of folks just wanting to play > with the new version, so that description is not entirely accurate. > > > > > When I run python setup.py develop I get > > > > 192:~/src/turbogears michela$ python setup.py develop > > Traceback (most recent call last): > > File "setup.py", line 12, in ? > > execfile(os.path.join("turbogears", "release.py")) > > IOError: [Errno 2] No such file or directory: 'turbogears/release.py' > > > > Which makes perfect sense because its unreleased. I'm confused. > > Version information had appeared in two places: setup.py and > turbogears/__init__.py. This was annoying and these have been known to > get out of sync, so I created release.py to hold all of that > information. According to my copy of the turbogears, that file is in > the repository (and setup.py has been working fine for me!) > > > And these are the only fields in the actual database > > > > id > > title > > description > > user_id > > > > Any help appreciated. I'm not sure if this is the root of the > > RelatedJoin issue I'm stuck on (posted twice about). > > http://groups.google.com/group/turbogears/msg/f1ada8e653811c84?dmode=source > > Try running tg-admin sql sql to see if the create statements that come > out look like what you have in the database. > > Kevin
Aah... Thanks Kevin. Uncovered lots of stuff wrong and now looking at the nicely re-skinned Catwalk and co. * If you leave the brackets off the column object type in SQLobject (e.g. DateTimeCol instead of DateTimeCol()) that column is just ignored * one of the downsides of simply updating from svn, you may end up with files in the wrong place if they are being moved around. I was somehow running a setup.py in the parent folder
