On 5/29/06, Ben Sizer <[EMAIL PROTECTED]> wrote: > > I just tried updating TG to the latest preview version, from the last > released version. It installed ok, but the upgrade instructions given > at http://www.turbogears.org/preview/download/upgrade.html were really > quite dangerous. > > > Firstly, it tried to pretty much eliminate my project: > > Replace 14853 bytes with 427 bytes (384/389 lines changed; 372 lines > removed) > Overwrite ../areagen\areagen\controllers.py [y/n/d/B/?] > > Replace 1818 bytes with 200 bytes (49/58 lines changed; 45 lines > removed) > Overwrite ../areagen\areagen\model.py [y/n/d/B/?] > > I know you can make a backup, but what's the point of an update script > if it does such a poor job at actually updating? For example, all it > wanted to do to model.py was add "from turbogears import identity", > give me a useless "YourDataClass" class, and remove the rest of my > file! That's no upgrade!
The upgrade instructions were pretty explicit about how you'll likely want to answer for each file. By running tg-admin upgrade, you're getting the latest version of setup.py, the new app.cfg file, the new release.py file. So, there is some value in the files it adds. One thing we could do, heading into a 1.0 stable release, is create a wrapper script that handles the transition from 0.8 to 1.0 more seamlessly (basically taking the steps in the upgrade doc into account directly in the script). > Then, it crashed out with this traceback: > Error (exit code: 1) > Traceback (most recent call last): > File "setup.py", line 2, in ? > from turbogears.finddata import find_package_data > File > "e:\code\python\python24\lib\site-packages\TurboGears-0.9a6-py2.4.egg\tur > bogears\__init__.py", line 6, in ? > from turbogears.controllers import expose, flash, validate, > redirect, \ > File > "e:\code\python\python24\lib\site-packages\TurboGears-0.9a6-py2.4.egg\tur > bogears\controllers.py", line 9, in ? > import kid > File > "e:\code\python\python24\lib\site-packages\kid-0.9.1-py2.4.egg\kid\__init > __.py", line 27, in ? > from kid.pull import ElementStream, Element, SubElement, Fragment, > \ > File > "e:\code\python\python24\lib\site-packages\kid-0.9.1-py2.4.egg\kid\pull.p > y", line 11, in ? > from kid.et import * # ElementTree > File > "e:\code\python\python24\lib\site-packages\kid-0.9.1-py2.4.egg\kid\et.py" > , line 11, in ? > import elementtree.ElementTree as ET > ImportError: No module named elementtree.ElementTree > > No idea why that has happened, since I've just upgraded TG as specified > and everything it needs should be there, if the setup script is doing > its job. Right? That's pretty odd. Are you able to run a TurboGears app? > So I'm very concerned that the upgrade instructions are essentially > prompting to overwrite our projects, and then potentially crash half > way through anyway. This is the first report I've seen of someone's elementtree disappearing... and I think you're leaving out the fact that the upgrade doc actually recommends answers for many of the files. Kevin --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
