migrate quickstarted projects from 2.0 to 2.1

[Pipoun]

Hi all,

The update from 2.0 to 2.1 is simple and documented:
(tg2env)$ easy_install -U -i http://www.turbogears.org/2.1/downloads/current/index
tg.devtools

But I'm wondering if we have to update the files that have been
automatically generated with 'paster quickstart'.

So is there any differences between a quickstart project in 2.0 and
2.1?
Should I update theses files? How can I do that automatically?

Thanks in advance!

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "TurboGears" group.
To post to this group, send email to turbogears@...
To unsubscribe from this group, send email to turbogears+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/turbogears?hl=en
-~----------~----~----~----~------~----~------~--~---

[Jorge Vargas]

On Wed, Oct 28, 2009 at 8:41 AM, pipoun <pipoun@...> wrote:

>
> Hi all,
>
> The update from 2.0 to 2.1 is simple and documented:
> (tg2env)$ easy_install -U -i http://www.turbogears.org/2.1/downloads/current/index
> tg.devtools
>
> But I'm wondering if we have to update the files that have been
> automatically generated with 'paster quickstart'.
>
> So is there any differences between a quickstart project in 2.0 and
> 2.1?

Yes, several minor things have changed. In general it should only be
adding more things, however quickstart will evolve overtime and the
changelog/release notes will only point out the critical changes.

> Should I update theses files? How can I do that automatically?
>
You should updated them. And no there is no way to update them
automatically as there is no way for the tool to know if it should
overrides your changes or not.

> Thanks in advance!
>
> >
>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "TurboGears" group.
To post to this group, send email to turbogears@...
To unsubscribe from this group, send email to turbogears+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/turbogears?hl=en
-~----------~----~----~----~------~----~------~--~---

[Pipoun]

On Oct 29, 8:49 am, Jorge Vargas <jorge.var...@...> wrote:
> On Wed, Oct 28, 2009 at 8:41 AM, pipoun <pip...@...> wrote:
>
> > Should I update theses files? How can I do that automatically?
>
> You should updated them. And no there is no way to update them
> automatically as there is no way for the tool to know if it should
> overrides your changes or not.

Thanks for the info

I've tried to quickstart a new project in another folder, but it
doesn't work because paster doesn't want to create a new project with
the same project/package/module name.
I had to create a new virtualenv and quickstart from it. Now I have to
merge the files...
I hope there will be a more practical way to do that in the future.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "TurboGears" group.
To post to this group, send email to turbogears@...
To unsubscribe from this group, send email to turbogears+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/turbogears?hl=en
-~----------~----~----~----~------~----~------~--~---

[Jorge Vargas]

On Fri, Oct 30, 2009 at 5:00 AM, pipoun <pipoun@...> wrote:

>
> On Oct 29, 8:49 am, Jorge Vargas <jorge.var...@...> wrote:
>> On Wed, Oct 28, 2009 at 8:41 AM, pipoun <pip...@...> wrote:
>>
>> > Should I update theses files? How can I do that automatically?
>>
>> You should updated them. And no there is no way to update them
>> automatically as there is no way for the tool to know if it should
>> overrides your changes or not.
>
> Thanks for the info
>
> I've tried to quickstart a new project in another folder, but it
> doesn't work because paster doesn't want to create a new project with
> the same project/package/module name.

yes that is the worst part. I normally rename the old one to something else.

> I had to create a new virtualenv and quickstart from it. Now I have to
> merge the files...
> I hope there will be a more practical way to do that in the future.

completely agree, however it's a complex problem. Other than having a
branch in your dvcs where you can merge from I can't think of another
solution. The problem is really that the QS code has no idea if you
modified the files so it can't overwrite them. And in some cases you
DO want to get rid of them.

> >
>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "TurboGears" group.
To post to this group, send email to turbogears@...
To unsubscribe from this group, send email to turbogears+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/turbogears?hl=en
-~----------~----~----~----~------~----~------~--~---

[Pipoun]

On 31 oct, 21:45, Jorge Vargas <jorge.var...@...> wrote:

> On Fri, Oct 30, 2009 at 5:00 AM, pipoun <pip...@...> wrote:
>
> > I had to create a new virtualenv and quickstart from it. Now I have to
> > merge the files...
> > I hope there will be a more practical way to do that in the future.
>
> completely agree, however it's a complex problem. Other than having a
> branch in your dvcs where you can merge from I can't think of another
> solution. The problem is really that the QS code has no idea if you
> modified the files so it can't overwrite them. And in some cases you
> DO want to get rid of them.

Thanks again for your feedback.
I'm not yet comfortable with the paster quickstart process but here's
my 2cents:
What about storing the hash (md5, ...) and the hierarchy of files
created in another folder?
Then paster could compare anytime if the files have been modified
since the initial creation.

When you QS again, if the files have not been modified, paster
overwrite them, and if not, there would be some sort of user
interaction process for merging the files.

>
>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "TurboGears" group.
To post to this group, send email to turbogears@...
To unsubscribe from this group, send email to turbogears+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/turbogears?hl=en
-~----------~----~----~----~------~----~------~--~---

[Jorge Vargas]

On Sun, Nov 1, 2009 at 6:01 PM, pipoun <pipoun@...> wrote:

>
>
>
> On 31 oct, 21:45, Jorge Vargas <jorge.var...@...> wrote:
>> On Fri, Oct 30, 2009 at 5:00 AM, pipoun <pip...@...> wrote:
>>
>> > I had to create a new virtualenv and quickstart from it. Now I have to
>> > merge the files...
>> > I hope there will be a more practical way to do that in the future.
>>
>> completely agree, however it's a complex problem. Other than having a
>> branch in your dvcs where you can merge from I can't think of another
>> solution. The problem is really that the QS code has no idea if you
>> modified the files so it can't overwrite them. And in some cases you
>> DO want to get rid of them.
>
> Thanks again for your feedback.
> I'm not yet comfortable with the paster quickstart process but here's
> my 2cents:
> What about storing the hash (md5, ...) and the hierarchy of files
> created in another folder?
> Then paster could compare anytime if the files have been modified
> since the initial creation.
>
> When you QS again, if the files have not been modified, paster
> overwrite them, and if not, there would be some sort of user
> interaction process for merging the files.
>

The problem comes with the merge. How can you be sure of it? is it
really worth it to spend all that time making this merging tool when
you can simply do it in your version control system? All in all keep
in mind quickstart as it's name implies is supposed to be a quick
start, it will get you going with the basic project upgrading projects
IMO is outside it's scope.

>>
>>
> >
>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "TurboGears" group.
To post to this group, send email to turbogears@...
To unsubscribe from this group, send email to turbogears+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/turbogears?hl=en
-~----------~----~----~----~------~----~------~--~---

[Adrian von Bidder]

On Thursday 05 November 2009 03.58:24 Jorge Vargas wrote:
> All in all keep
> in mind quickstart as it's name implies is supposed to be a quick
> start, it will get you going with the basic project upgrading projects
> IMO is outside it's scope.
>

Agree.

But if there are changes that must (or should) be made to quickstarted
projects on release updates they must be well-documented.
 * changes that must be made for compatibility
 * changes that are recommended/suggested to take advantage of new features
or conform to new best practice

... and if the changes are big (afaict they aren't, so far), the question
should probably be discussed why the qs needs to be changed so much and if
functionality X couldn't be done by some packaged piece of code instead of
boilerplate to be repeated in every project.

(I'm thinking here mostly from the deployment perspective.  All code that is
not under the control of packaging systems etc. will not be maintained.  
That is also the reason why I would never run a virtualenv based set-up in
production systems: I have one source for security upgrades on production
systems, and this is the distributor of the OS.  Everything that I have to
maintain separately is a huge PITA.)

cheers
-- vbi

--
Things that try to look like things
often do look more like things than things.
        -- Granny Weatherwax

[Robert Forkel]

a very notable difference which should be documented (at least here :)):
to make the "@expose('json')" decorator work,

#Enable json in expose
base_config.renderers.append('json')

must be added to the app config explicitely.

regards,
robert

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "TurboGears" group.
To post to this group, send email to turbogears@...
To unsubscribe from this group, send email to turbogears+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/turbogears?hl=en
-~----------~----~----~----~------~----~------~--~---