Yes, you're right... no point in duplicating code. I think the util one didn't exist when the quickstart one was created...
Kevin On Dec 7, 2006, at 11:36 AM, Jorge Vargas wrote: > > This was pointed out by Jeff I didn't knew about it. > > shouldn't the quickstart projects use util, or util be removed It > seems stupid to have it both way > > http://trac.turbogears.org/turbogears/browser/trunk/turbogears/ > qstemplates/quickstart/start-%2Bpackage%2B.py_tmpl > > http://trac.turbogears.org/turbogears/browser/trunk/turbogears/ > util.py#L75 > > ---------- Forwarded message ---------- > From: Jeff Hinrichs - DM&T <[EMAIL PROTECTED]> > Date: Dec 7, 2006 9:43 AM > Subject: Re: turbogears tickets and mailing list > To: Jorge Vargas <[EMAIL PROTECTED]> > > > On 12/6/06, Jorge Vargas <[EMAIL PROTECTED]> wrote: >> On 12/5/06, Jeff Hinrichs - DM&T <[EMAIL PROTECTED]> wrote: >>> On 12/4/06, Jorge Vargas <[EMAIL PROTECTED]> wrote: >>>> hi >>>> >>>> I have seen your new to our project and have posted several >>>> tickets/messages. >>>> >>>> will it be ok if you follow this procedure? it will keep the >>>> ammount >>>> of work we all have to do smaller. >>>> >>>> Ask in IRC or post to the mailing list (not together) then if the >>>> issue is consider a real bug or proposal post a bug to trac. >>>> >>>> it's simplier for me to keep trac of all the tickets and it's also >>>> simplier to keep people from replying in different places to the >>>> same >>>> questions. >>>> >>>> thanks >>>> >>> >>> Jorge, >>> Sure no problem. I tried to close/invalidate the tickets -- >>> sorry for >>> any trouble I caused. The TG book caused quite a bit of confusion >>> with regards to deployment -- the use of prod.cfg is based on the >>> non-existence of setup.py (according to the code) not by deleting >>> the >>> dev.cfg as specified in the book. This caused quite a bit of >>> confusion for me until I started reading the through the code. >>> >> actually your missing a step, ones you create the egg file the >> setup.py is gone therefore from then on it's based on the >> existance of >> dev.cfg. remenber you always deploy as egg files. > Did not know that -- perhaps I skipped over it in the book but the > part on Production was pretty explicit and made it seem that only the > removal of dev.cfg was necessary. I would make note that if you do > that, TG pushes on as if it's read dev.cfg and then errors out later > complaining about no autoreload statement.(misleading) This is why > I, incorrectly, assumed there was a problem in the prod.cfg and it > needed an autoreload statement. If you look at the > load_project_config(configfile=None) function in util.py it tries to > catch the missing config and throw an error -- which wasn't happening. > (I assumed, incorrectly, that this was the code being used based on > grep'ing the TG source for dev.cfg) > > The cfg code is now in the startup-project.py file and there isn't an > error checking going on like what is done with the code in utils.py. > While not a bug per se, it does seem to make TG less robust. > > Not that any of this excuses my misuse of the bug reporting system. > >>> By the way, that logic code is in multiple places -- it's in the >>> util.py in the TG package and is also in the startup-ProjectName.py >>> file in the project directory. >>> >> umm really? I haven't notice so we can reduce the startup-scripts to >> call the util code. > > http://trac.turbogears.org/turbogears/browser/trunk/turbogears/util.py > get_project_config() > > and > http://trac.turbogears.org/turbogears/browser/trunk/turbogears/ > qstemplates/quickstart/start-%2Bpackage%2B.py_tmpl > > >>> Also, while I have you. Why does webconsole not read the >>> dev.cfg/prod.cfg for the project fully? I had to >>> tg.config.update_config(sp?) to get it to recognize anything but the >>> db settings. It would seem logical for webconsole to read in the >>> proper .cfg (based on the same logic as startup-projectname.py does. >> yea this is one of those things that keeps poping up. the webconsole >> was develop as a prove of concept that it can be done, honestly I >> never give it much atention but as far as I know it was supposed to >> emulate 100% tg-admin shell, maybe there was a change in the shell >> that wasn't applied to the webconsole? >> > Don't know about that -- I just assumed that since you ran it from > within the project that it would automatically take in the the config > files and such from the project. Probably a misconception on my part. >>> >>> Thanks, >>> >>> Jeff >>> >>> p.s. apologies again. >>> >> > > > -- > Jeff Hinrichs > > > -- Kevin Dangoor TurboGears / Zesty News email: [EMAIL PROTECTED] company: http://www.BlazingThings.com blog: http://www.BlueSkyOnMars.com --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears Trunk" 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-trunk?hl=en -~----------~----~----~----~------~----~------~--~---
