On Thu, Dec 13, 2007 at 11:47:58AM +0100, Marcin Kasperski wrote:
> Maybe I missed something, but ....
>
> ... what should I do to upgrade existing project to the new
> Pylons release? I mean, for example, patching middleware.py so
> it suits newer idioms, patching imports etc.
Install the new Pylons version. Then pretend you are creating
(overwriting) a brand new Pylons project. Go into the parent directory
of where your development.init is located and run something like:
$> paster create -t pylons myapplication
Paster will then show you diffs of what has changed so you have a chance
to include the changes without breaking your stuff.
> I considered forcing some 3-way merge (old 'post-paster-create'
> version, current 'post-paster-create' version and the actual project),
> but it seems a bit tedious to setup. Maybe there is some simpler way?
This is. Although I'd prefer if I could launch vimdiff or kompare during
the upgrade. It's pretty good that it exists already anyway. It does no
3-way-diff/merge though. So if you changed something in the files then
the "paster create" upgrade will suggest to throw away your changes
unless you carefully include them. :(
Cheers
Christoph
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"pylons-discuss" group.
To post to this group, send email to pylons-discuss@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/pylons-discuss?hl=en
-~----------~----~----~----~------~----~------~--~---
