Hi Christoph,

as you mention it's probably not the «right» place to ask but I tought
it would be a good question to ask to people here who use Pylons like
me and had to make a choice about this question. I don't search
technical advice but experience from people who use one of them, like
you =). Pylons switched from SVN to Mercurial... there is probably a
reason?

Thanks for your answer,

Blaise

On May 5, 7:55 am, Christoph Haas <[EMAIL PROTECTED]> wrote:
> Hi... errr... blaf?
>
> On Montag, 5. Mai 2008, blaf wrote:
>
> > I'm in the move to install Mercurial or Bazaar for versioning a shared
> > Pylons project. Actually I've never used both in real production, just
> > installed them and played a bit to see how they work. Both seems good
> > but I can't figure out how to make a choice.
>
> > Any advice will be appreciated.
>
> This is probably not the right mailing list to get advise for DRCSs but
> anyway. :) setuptools - which is used for deployment of a Pylons
> application - only knows about Subversion. So in this case Mercurial and
> Bazaar-NG are supported equally worse. There is a patch for setuptools
> apparently to use Mercurial though. This just applies to using the version
> number in the releases automatically. Otherwise you can use whatever you
> want.
>
> I use Mercurial. Bazaar has let me down before. And Git is too cryptic.
> Mercurial suits me well. I just get stuck with multiple "heads" from time
> to time but that's nothing that I couldn't solve. Mercurial is lightweight
> and fast and well supported and - above all - written in Python. :)
>
> Cheers
>  Christoph
>
>  signature.asc
> 1KDownload
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"pylons-discuss" 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/pylons-discuss?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to