Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.python > #4044 > unrolled thread

Development tools and practices for Pythonistas

Back to article view | Back to comp.lang.python

Contents

  Development tools and practices for Pythonistas snorble <snorble@hotmail.com> - 2011-04-26 07:39 -0700
    Re: Development tools and practices for Pythonistas rusi <rustompmody@gmail.com> - 2011-04-26 09:00 -0700
    Re: Development tools and practices for Pythonistas "Martin P. Hellwig" <martin.hellwig@gmail.com> - 2011-04-26 17:02 +0000
    Re: Development tools and practices for Pythonistas Thomas Rachel <nutznetz-0c1b6768-bfa9-48d5-a470-7603bd3aa915@spamschutz.glglgl.de> - 2011-04-26 19:59 +0200
      Re: Development tools and practices for Pythonistas Algis Kabaila <akabaila@pcug.org.au> - 2011-04-27 04:42 +1000
        Re: Development tools and practices for Pythonistas Thomas Rachel <nutznetz-0c1b6768-bfa9-48d5-a470-7603bd3aa915@spamschutz.glglgl.de> - 2011-04-27 00:32 +0200
      Re: [OT] Comparing VCS tools (was ""Development tools and practices for Pythonistas") Tim Chase <python.list@tim.thechases.com> - 2011-04-26 20:44 -0500
        Re: [OT] Comparing VCS tools Ben Finney <ben+python@benfinney.id.au> - 2011-04-27 12:45 +1000
          Re: [OT] Comparing VCS tools Ben Finney <ben+python@benfinney.id.au> - 2011-04-27 16:51 +1000
          Re: [OT] Comparing VCS tools Tim Chase <python.list@tim.thechases.com> - 2011-04-27 14:13 -0500
        Re: Comparing VCS tools (was ""Development tools and practices for Pythonistas") rusi <rustompmody@gmail.com> - 2011-04-26 19:50 -0700
          Re: Comparing VCS tools (was ""Development tools and practices for Pythonistas") alex23 <wuwei23@gmail.com> - 2011-04-26 22:37 -0700
        Re: [OT] Comparing VCS tools (was ""Development tools and practices  for Pythonistas") Kevin Walzer <kw@codebykevin.com> - 2011-04-29 09:26 -0400
          Re: [OT] Comparing VCS tools (was ""Development tools and practices for Pythonistas") Daniel Kluev <dan.kluev@gmail.com> - 2011-04-30 05:08 +1100
    Re: Development tools and practices for Pythonistas Jean-Michel Pichavant <jeanmichel@sequans.com> - 2011-04-26 20:04 +0200
    Re: Development tools and practices for Pythonistas CM <cmpython@gmail.com> - 2011-04-26 11:29 -0700
      Re: Development tools and practices for Pythonistas CM <cmpython@gmail.com> - 2011-04-26 11:31 -0700
        Re: Development tools and practices for Pythonistas Algis Kabaila <akabaila@pcug.org.au> - 2011-04-27 04:50 +1000
    Re: Development tools and practices for Pythonistas Chris Angelico <rosuav@gmail.com> - 2011-04-27 06:14 +1000
      Re: Development tools and practices for Pythonistas Ben Finney <ben+python@benfinney.id.au> - 2011-04-27 09:41 +1000
        Re: Development tools and practices for Pythonistas Algis Kabaila <akabaila@pcug.org.au> - 2011-04-27 10:44 +1000
        Re: Development tools and practices for Pythonistas Jean-Michel Pichavant <jeanmichel@sequans.com> - 2011-04-27 11:24 +0200
          Re: Development tools and practices for Pythonistas Anssi Saari <as@sci.fi> - 2011-04-27 15:13 +0300
            Re: Development tools and practices for Pythonistas Jean-Michel Pichavant <jeanmichel@sequans.com> - 2011-04-27 14:24 +0200
              Re: Development tools and practices for Pythonistas Hans Georg Schaathun <hg@schaathun.net> - 2011-04-30 08:37 +0100
                Re: Development tools and practices for Pythonistas Martin Schöön <martin.schoon@gmail.com> - 2011-04-30 09:15 +0000
                  Re: [OT] VCS for non-text (was Development tools and practices for Pythonistas) Tim Chase <python.list@tim.thechases.com> - 2011-04-30 09:18 -0500
                    Re: [OT] VCS for non-text (was Development tools and practices for Pythonistas) Martin Schöön <martin.schoon@gmail.com> - 2011-05-01 19:53 +0000
              Re: Development tools and practices for Pythonistas Hans Georg Schaathun <hg@schaathun.net> - 2011-04-29 19:35 +0100
                Re: Development tools and practices for Pythonistas Ben Finney <ben+python@benfinney.id.au> - 2011-04-30 09:17 +1000
                  Re: Development tools and practices for Pythonistas CM <cmpython@gmail.com> - 2011-04-29 20:21 -0700
                    Re: Development tools and practices for Pythonistas Roy Smith <roy@panix.com> - 2011-04-29 23:54 -0400
                      Re: Development tools and practices for Pythonistas Ben Finney <ben+python@benfinney.id.au> - 2011-05-01 10:36 +1000
                        Re: Development tools and practices for Pythonistas Shawn Milochik <shawn@milochik.com> - 2011-04-30 20:47 -0400
                          Re: Development tools and practices for Pythonistas Dietmar Schwertberger <news@schwertberger.de> - 2011-05-01 18:11 +0200
                            Re: Development tools and practices for Pythonistas Jason Earl <jearl@notengoamigos.org> - 2011-05-01 14:51 -0600
                            Re: Development tools and practices for Pythonistas Ben Finney <ben+python@benfinney.id.au> - 2011-05-02 07:49 +1000
                              Re: Development tools and practices for Pythonistas Paul Rubin <no.email@nospam.invalid> - 2011-05-01 19:37 -0700
                            Re: Development tools and practices for Pythonistas David Boddie <david@boddie.org.uk> - 2011-05-02 01:33 +0200
                              Re: Development tools and practices for Pythonistas Dietmar Schwertberger <news@schwertberger.de> - 2011-05-02 19:40 +0200
                    Re: Development tools and practices for Pythonistas Shawn Milochik <shawn@milochik.com> - 2011-04-29 23:49 -0400
                    Re: Development tools and practices for Pythonistas rusi <rustompmody@gmail.com> - 2011-05-01 20:06 -0700
                      Re: Development tools and practices for Pythonistas Ben Finney <ben+python@benfinney.id.au> - 2011-05-02 13:22 +1000
                        Re: Development tools and practices for Pythonistas rusi <rustompmody@gmail.com> - 2011-05-01 20:45 -0700
                        Re: Development tools and practices for Pythonistas Algis Kabaila <akabaila@pcug.org.au> - 2011-05-02 17:08 +1000
                          Re: Development tools and practices for Pythonistas rusi <rustompmody@gmail.com> - 2011-05-02 00:19 -0700
                            Re: Development tools and practices for Pythonistas Algis Kabaila <akabaila@pcug.org.au> - 2011-05-02 17:48 +1000
                              Re: Development tools and practices for Pythonistas jacek2v <jacek2v@gmail.com> - 2011-05-02 02:09 -0700
                                Re: Development tools and practices for Pythonistas Algis Kabaila <akabaila@pcug.org.au> - 2011-05-02 20:38 +1000
                                  Re: Development tools and practices for Pythonistas jacek2v <jacek2v@gmail.com> - 2011-05-03 11:31 -0700
                      Re: Development tools and practices for Pythonistas Anssi Saari <as@sci.fi> - 2011-05-03 21:19 +0300
                        Re: Development tools and practices for Pythonistas rusi <rustompmody@gmail.com> - 2011-05-03 11:50 -0700
                          Re: Development tools and practices for Pythonistas Anssi Saari <as@sci.fi> - 2011-05-04 21:06 +0300
          Re: Development tools and practices for Pythonistas Ben Finney <ben+python@benfinney.id.au> - 2011-04-27 22:14 +1000
        Re: Development tools and practices for Pythonistas Chris Angelico <rosuav@gmail.com> - 2011-04-27 19:33 +1000
        Re: Development tools and practices for Pythonistas Jean-Michel Pichavant <jeanmichel@sequans.com> - 2011-04-27 13:17 +0200
          Re: Development tools and practices for Pythonistas Thomas Rachel <nutznetz-0c1b6768-bfa9-48d5-a470-7603bd3aa915@spamschutz.glglgl.de> - 2011-04-27 20:08 +0200
            Re: Development tools and practices for Pythonistas Ben Finney <ben+python@benfinney.id.au> - 2011-04-28 09:44 +1000
        Re: [OT] VCS tools (was "Development tools and practices for Pythonistas") Tim Chase <python.list@tim.thechases.com> - 2011-04-27 14:07 -0500
          Re: [OT] VCS tools (was "Development tools and practices for Pythonistas") Martin Schöön <martin.schoon@gmail.com> - 2011-04-28 20:48 +0000
            Re: [OT] VCS tools Ben Finney <ben+python@benfinney.id.au> - 2011-04-29 07:50 +1000
              Re: [OT] VCS tools Tim Chase <python.list@tim.thechases.com> - 2011-04-28 18:09 -0500
              Re: [OT] VCS tools Daniel Kluev <dan.kluev@gmail.com> - 2011-04-29 11:37 +1100
              Re: [OT] From svn to something else? (was: VCS tools) Hans Georg Schaathun <georg@schaathun.net> - 2011-04-29 11:07 +0100
                Re: [OT] From svn to something else? Tim Chase <python.list@tim.thechases.com> - 2011-04-29 06:50 -0500
                  Re: [OT] From svn to something else? Hans Georg Schaathun <hg@schaathun.net> - 2011-04-29 18:01 +0100
                    Re: [OT] From svn to something else? Tim Chase <python.list@tim.thechases.com> - 2011-04-29 13:23 -0500
                Re: [OT] From svn to something else? Ben Finney <ben+python@benfinney.id.au> - 2011-04-29 22:53 +1000
                  Re: [OT] From svn to something else? "D'Arcy J.M. Cain" <darcy@druid.net> - 2011-04-29 09:26 -0400
              Re: [OT] VCS tools Martin Schöön <martin.schoon@gmail.com> - 2011-04-29 18:46 +0000
    Re: Development tools and practices for Pythonistas Dan Stromberg <drsalists@gmail.com> - 2011-04-26 14:00 -0700
    recommended Emacs mode (was Re: Development tools and practices for Pythonistas) Gour-Gadadhara Dasa <gour@atmarama.net> - 2011-04-27 08:39 +0200
      Re: recommended Emacs mode (was Re: Development tools and practices for Pythonistas) rusi <rustompmody@gmail.com> - 2011-04-27 00:51 -0700
        Re: recommended Emacs mode Gour-Gadadhara Dasa <gour@atmarama.net> - 2011-04-27 10:10 +0200
    Re: Development tools and practices for Pythonistas Jonathan Hartley <tartley@tartley.com> - 2011-05-06 02:51 -0700
      Re: Development tools and practices for Pythonistas Tim Golden <mail@timgolden.me.uk> - 2011-05-06 10:59 +0100
        Python packaging (was Development tools and practices for Pythonistas) rusi <rustompmody@gmail.com> - 2011-05-06 04:55 -0700
    Re: Development tools and practices for Pythonistas rusi <rustompmody@gmail.com> - 2011-05-08 00:43 -0700
    Re: Development tools and practices for Pythonistas Roy Smith <roy@panix.com> - 2011-05-08 09:31 -0400
      Non Programming in python rusi <rustompmody@gmail.com> - 2011-05-10 09:41 -0700
        Re: Non Programming in python Terry Reedy <tjreedy@udel.edu> - 2011-05-10 15:28 -0400
          Re: Non Programming in python rusi <rustompmody@gmail.com> - 2011-05-10 20:36 -0700
        Re: Non Programming in python Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2011-05-10 22:53 +0000

Page 2 of 5 — ← Prev page 1 [2] 3 4 5  Next page →

#4100

On Wednesday 27 April 2011 09:41:53 Ben Finney wrote:
> Chris Angelico <rosuav@gmail.com> writes:
> > As other people have said, version control is very handy. I
> > use git myself, but imho the choice of _which_ VCS you use
> > is far less important than the choice of _whether_ to use
> > one.
> 
> True enough. But the modern crop of first-tier VCSen –
> Bazaar, Git, Mercurial – are the ones to choose from.
> Anoyone recommending a VCS tool that has poor merging
> support (such as Subversion or, heaven help us, CVS) is
> doing the newcomer a disservice.
> 
All golden advice!  Two things were not mentioned:

1. Work on an existing project that is based on Python. The 
"Launchpad" of ubuntu has a great environment for a project. 
There are many existing projects in which to participate.  Even 
Bazaar's GUI version is programmed in Python with PyQt for the 
GUI proper.  You will get a lot out of participation in an 
existing project, probably a lot more than you input.  
Ultimately it is how much you input that is of of most benefit 
to you yourself.

2. I failed to see questions and suggestions of platform to work 
from.  Your experience, interests,  and computer platform will 
determine what is useful to you and what is less useful.

3. Finally, it is important to have a project about which you 
can master enough enthusiasm to persist.  "What project " 
depends very much on item 2.

May the favourable wind fill your sails,

OldAl.
-- 
Algis
http://akabaila.pcug.org.au/StructuralAnalysis.pdf

[toc] | [prev] | [next] | [standalone]

#4119

Ben Finney wrote:
> Mercurial – are the ones to choose from. Anoyone recommending a VCS tool
> that has poor merging support (such as Subversion or, heaven help us,
> CVS) is doing the newcomer a disservice.
>   
> True enough. But the modern crop of first-tier VCSen – Bazaar, Git,
For a single user, there would be no merge issue. And svn is very simple 
to use.
That would not be a such bad advice for a beginner with VCS systems.

JM

[toc] | [prev] | [next] | [standalone]

#4127

Jean-Michel Pichavant <jeanmichel@sequans.com> writes:

> For a single user, there would be no merge issue.

Really? What about a single user with many computers and environments?
I find myself merging files on occasion because I edited them
separately and forgot to check in changes before doing more edits on a
different computer.

[toc] | [prev] | [next] | [standalone]

#4130

Anssi Saari wrote:
> Jean-Michel Pichavant <jeanmichel@sequans.com> writes:
>
>   
>> For a single user, there would be no merge issue.
>>     
>
> Really? What about a single user with many computers and environments?
> I find myself merging files on occasion because I edited them
> separately and forgot to check in changes before doing more edits on a
> different computer.
>   
I was talking about merge *issue* i.e merge resulting in conflicts that 
are not easy to solve. With a single user most of the merge will be 
solved automatically by any decent VCS.

JM

[toc] | [prev] | [next] | [standalone]

#4187

On Fri, 29 Apr 2011 20:21:58 -0700 (PDT), CM
  <cmpython@gmail.com> wrote:
:  While we're on the topic, when should a lone developer bother to start
:  using
:  a VCS?  At what point in the complexity of a project (say a hobby
:  project, but
:  a somewhat seriousish one, around ~5-9k LOC) is the added complexity
:  of
:  bringing a VCS into it worth it?

You are asking the wrong question.  It depends relatively little on the
number of lines, and much more on what you are likely to do with it.

One thing is certain.  If you are ever going to want to use a VCS,
you can just as well start yesterday.  Using a VCS is not an extra
hassle to use.  Only an added hassle to get started with.

Personally I use the VCS as
  1) My backup system; naturally doing incremental backups only.
  2) A means to synchronise multiple boxes (not just my laptop and
    my desktop, sometimes a linux and a mac system, and dedicated
    number crunchers too), and merge changes made out of synch.
  3) The possibility to make one branch to run a suite of jobs
    which may take a week or more, and still continue development
    independently on the main branch.

As you can see, the number of lines is irrelevant.  1-2 mean that
everything is VC-d, not only code for which the VCS is meant.
And 3 is of course about what kind of code.

I branch rather little.  Programming is not my day job -- nor my
main hobby, and I simply have not got the capacity to keep track
of multiple branches.   Even at 12-15kloc I have little use of
the VCS for its intended purposes.  If you take your development
project more seriously, you may do more of that within the first
500 loc...

But then, using VCS is not sufficient.  You need to /think/ VC.

In other words, taking up a VCS when the system is large enough
to require it is too late.  You need time to learn the thinking.

-- 
:-- Hans Georg

[toc] | [prev] | [next] | [standalone]

#4355

On 2011-04-30, Hans Georg Schaathun <hg@schaathun.net> wrote:
> On Fri, 29 Apr 2011 20:21:58 -0700 (PDT), CM
>  <cmpython@gmail.com> wrote:
>:  While we're on the topic, when should a lone developer bother to start
>:  using
>:  a VCS?  At what point in the complexity of a project (say a hobby
>:  project, but
>:  a somewhat seriousish one, around ~5-9k LOC) is the added complexity
>:  of
>:  bringing a VCS into it worth it?
>
> You are asking the wrong question.  It depends relatively little on the
> number of lines, and much more on what you are likely to do with it.
>
You guys are very code focused, which is natural given where we are.

Having absorbed what I have seen here, looked a little at Mercurial,
read a little on the webs of Fossil and Bazaar I start to think there
is great merit in all this VCS stuff for other types of projects.

At work my projects contain very little coding (some Python, some
matlab/scilab perhaps) but a fair amount of CAD/CAE, written
reports, presentations (OpenOffice and that other Office),
spread sheets etc etc. A mixture of ascii-files and various
proprietary formats most of which is stored in binary form.
Some of the CAE-work generate pretty big files stored
in dynamically created subdirectories.

Our computer environment is mostly based on Vista and Suse Linux
and I still have a SUN Solaris machine in my office but probably
not for long.

Given this type of scenario, what VCS tools should I consider?
Still the Mercurial/Git/Bazaar/Fossil crowd? Any one of those
ruled out and then why?

/Martin

[toc] | [prev] | [next] | [standalone]

#4360 — Re: [OT] VCS for non-text (was Development tools and practices for Pythonistas)

On 04/30/2011 04:15 AM, Martin Schöön wrote:
> You guys are very code focused, which is natural given where we are.
>
> Having absorbed what I have seen here, looked a little at Mercurial,
> read a little on the webs of Fossil and Bazaar I start to think there
> is great merit in all this VCS stuff for other types of projects.
>
> At work my projects contain very little coding (some Python, some
> matlab/scilab perhaps) but a fair amount of CAD/CAE, written
> reports, presentations (OpenOffice and that other Office),
> spread sheets etc etc. A mixture of ascii-files and various
> proprietary formats most of which is stored in binary form.
> Some of the CAE-work generate pretty big files stored
> in dynamically created subdirectories.

For non-text blobs, it takes a little bit of insight to get the 
most out of them.  For OpenDocument (Open/Libre Office 
documents), they're zipped files containing text/XML which can be 
diff'ed with more meaning.  Usually there are custom filters for 
git[1], Mercurial[2] and Bazaar[3] which will unpack the zipped 
file contents before committing and give you more sensible diffs. 
  Likewise, for images (gif/jpg/tiff/raw/etc), there are 
particular image-diff programs which make it easier to tell what 
happened, as the textual diff of binary files is pretty useless. 
  However some images (such as .svg files) are XML/text inside, 
and diff pretty nicely without extra effort.

I can't speak to CAD/CAE, but it would have to be addressed on a 
per-format basis in your given VCS.  That said, you *can* store 
the binary blobs in each, it's just not as useful without 
meaningful comparisons.

-tkc

[1]
http://kerneltrap.org/mailarchive/git/2008/9/15/3305014

[2]
http://mercurial.selenic.com/wiki/HandlingOpenDocumentFiles

[3]
http://doc.bazaar.canonical.com/plugins/en/oodiff.html

[toc] | [prev] | [next] | [standalone]

#4411 — Re: [OT] VCS for non-text (was Development tools and practices for Pythonistas)

On 2011-04-30, Tim Chase <python.list@tim.thechases.com> wrote:
> On 04/30/2011 04:15 AM, Martin Schöön wrote:
>> You guys are very code focused, which is natural given where we are.
>>
>> Having absorbed what I have seen here, looked a little at Mercurial,
>> read a little on the webs of Fossil and Bazaar I start to think there
>> is great merit in all this VCS stuff for other types of projects.
>>
>> At work my projects contain very little coding (some Python, some
>> matlab/scilab perhaps) but a fair amount of CAD/CAE, written
>> reports, presentations (OpenOffice and that other Office),
>> spread sheets etc etc. A mixture of ascii-files and various
>> proprietary formats most of which is stored in binary form.
>> Some of the CAE-work generate pretty big files stored
>> in dynamically created subdirectories.
>
> For non-text blobs, it takes a little bit of insight to get the 
> most out of them.  For OpenDocument (Open/Libre Office 
> documents), they're zipped files containing text/XML which can be 
> diff'ed with more meaning.  Usually there are custom filters for 
> git[1], Mercurial[2] and Bazaar[3] which will unpack the zipped 
> file contents before committing and give you more sensible diffs. 
>   Likewise, for images (gif/jpg/tiff/raw/etc), there are 
> particular image-diff programs which make it easier to tell what 
> happened, as the textual diff of binary files is pretty useless. 
>   However some images (such as .svg files) are XML/text inside, 
> and diff pretty nicely without extra effort.
>
> I can't speak to CAD/CAE, but it would have to be addressed on a 
> per-format basis in your given VCS.  That said, you *can* store 
> the binary blobs in each, it's just not as useful without 
> meaningful comparisons.
>
> -tkc
>
> [1]
> http://kerneltrap.org/mailarchive/git/2008/9/15/3305014
>
> [2]
> http://mercurial.selenic.com/wiki/HandlingOpenDocumentFiles
>
> [3]
> http://doc.bazaar.canonical.com/plugins/en/oodiff.html
>
All very useful information. Thank you for that Tim.

/Martin

[toc] | [prev] | [next] | [standalone]

#4320

On Wed, 27 Apr 2011 14:24:30 +0200, Jean-Michel Pichavant
  <jeanmichel@sequans.com> wrote:
:  I was talking about merge *issue* i.e merge resulting in conflicts that 
:  are not easy to solve. With a single user most of the merge will be 
:  solved automatically by any decent VCS.

Exactly, and with svn that can be a true nightmare when directories 
are involved.  The rumour is that git handles this much better.


I call it a rumour not because I doubt it (I don't), but because 
I have not seen for myself.

-- 
:-- Hans Georg

[toc] | [prev] | [next] | [standalone]

#4331

Hans Georg Schaathun <hg@schaathun.net> writes:

> Exactly, and with svn that can be a true nightmare when directories 
> are involved.  The rumour is that git handles this much better.

Any of the top-tier distributed VCS (Bazaar, Git, Mercurial) handle
branching and merging very well. They have to, because branching and
merging is much more frequent and casual in a distributed VCS.

A lone developer using such a VCS reaps the benefits of this by getting
good merging support.

-- 
 \       “If consumers even know there's a DRM, what it is, and how it |
  `\     works, we've already failed.” —Peter Lee, Disney corporation, |
_o__)                                                             2005 |
Ben Finney

[toc] | [prev] | [next] | [standalone]

#4337

> A lone developer using such a VCS reaps the benefits of this by getting
> good merging support.

While we're on the topic, when should a lone developer bother to start
using
a VCS?  At what point in the complexity of a project (say a hobby
project, but
a somewhat seriousish one, around ~5-9k LOC) is the added complexity
of
bringing a VCS into it worth it?

I've been making changes to code and saving changes to the same
files,
but backing up on Dropbox, which keeps 30 days of previous saves.
I've rarely had to resort to undoing code by calling up a previous
save.
I test each new change as it is made to see if it breaks anything
(not
automatic testing, though), and I don't collaborate with anyone else
as
yet.

Should I bother to try a VCS?

[toc] | [prev] | [next] | [standalone]

#4338

In article 
<ad197191-042c-468a-9002-f449b633d375@s4g2000yql.googlegroups.com>,
 CM <cmpython@gmail.com> wrote:

> While we're on the topic, when should a lone developer bother to start
> using a VCS?

No need to use VCS at the very beginning of a project.  You can easily 
wait until you've written 10 or 20 lines of code :-)

> Should I bother to try a VCS?

Absolutely.  Even if you don't need it for a small one-person project, 
it's a good habit to get into.

If you haven't used any, my recommendation would be hg.  Partly because 
it's powerful, and partly because it's relatively easy to use.  The 
other popular choice these days would be git.  Hg and git are pretty 
similar, and between the two of them probably cover 90% of current 
usage.  Unless you've got a specific reason to try something else (i.e. 
a project you're interested in uses something else), those seem like the 
only two reasonable choices.

[toc] | [prev] | [next] | [standalone]

#4374

Roy Smith <roy@panix.com> writes:

> No need to use VCS at the very beginning of a project. You can easily
> wait until you've written 10 or 20 lines of code :-)

+1 QOTW

> > Should I bother to try a VCS?
>
> Absolutely. Even if you don't need it for a small one-person project,
> it's a good habit to get into.

Yes. Learn to use each of the top-tier VCS options: Bazaar, Git,
Mercurial. Learn to use one of them well (my choice is Bazaar, as
explored elsewhere in this thread).

-- 
 \       “Whenever you read a good book, it's like the author is right |
  `\   there, in the room talking to you, which is why I don't like to |
_o__)                                   read good books.” —Jack Handey |
Ben Finney

[toc] | [prev] | [next] | [standalone]

#4375

For what it's worth, the Python core developers have selected Mercurial. 
I personally use git and love it. Most open-source people seem to use 
one or the other of the two. They're pretty similar in most ways.

Look at the big two sites for open-source repositories -- github and 
bitbucket. One's git, the other Mercurial. I don't think you can go 
wrong picking either one.

[toc] | [prev] | [next] | [standalone]

#4403

Am 01.05.2011 02:47, schrieb Shawn Milochik:
> Look at the big two sites for open-source repositories -- github and
> bitbucket. One's git, the other Mercurial. I don't think you can go
> wrong picking either one.

Can any of those be used from Python as a library, i.e. something like
import Hg
r = Hg.open(path)

When I had a look at Mercurial, which is implemented in Python,
it was implemented in a way that I could not do that. It was implemented
as rather monolithic program which could be used from os.system(...)
only.
With a good API, I could easily have integrated it into my development
flow. I have a codebase which is shared between different projects and
there are many small changes on many different PCs.
In theory a distributed VCS is good at supporting that, but in practice
I went back to my lightweight synchronization scripts and file storage
again. With the API, I could have best of both worlds.


Regards,

Dietmar

[toc] | [prev] | [next] | [standalone]

#4416

On Sun, May 01 2011, Dietmar Schwertberger wrote:

> Am 01.05.2011 02:47, schrieb Shawn Milochik:
>> Look at the big two sites for open-source repositories -- github and
>> bitbucket. One's git, the other Mercurial. I don't think you can go
>> wrong picking either one.
>
> Can any of those be used from Python as a library, i.e. something like
> import Hg
> r = Hg.open(path)
>
> When I had a look at Mercurial, which is implemented in Python, it was
> implemented in a way that I could not do that. It was implemented as
> rather monolithic program which could be used from os.system(...)
> only.
> 
> With a good API, I could easily have integrated it into my development
> flow. I have a codebase which is shared between different projects and
> there are many small changes on many different PCs.  In theory a
> distributed VCS is good at supporting that, but in practice I went
> back to my lightweight synchronization scripts and file storage
> again. With the API, I could have best of both worlds.

You should take a look at Bazaar.  I found it fairly easy to use bzrlib
from my own Python scripts.

http://people.canonical.com/~mwh/bzrlibapi/

Jason

[toc] | [prev] | [next] | [standalone]

#4419

Dietmar Schwertberger <news@schwertberger.de> writes:

> Am 01.05.2011 02:47, schrieb Shawn Milochik:
> > Look at the big two sites for open-source repositories -- github and
> > bitbucket.

Note that there are three: Launchpad (backed by Bazaar) is the other
“big site” for free-software project hosting.

> Can any of those be used from Python as a library, i.e. something like
> import Hg
> r = Hg.open(path)

I haven't used it, but Launchpad (the Canonical project hosting which
uses Bazaar for the VCS) is of course well-supported in the Bazaar
libraries. Access to the hosting site is eminently programmable with a
good API, by all accounts.

-- 
 \        “It is seldom that liberty of any kind is lost all at once.” |
  `\                                                       —David Hume |
_o__)                                                                  |
Ben Finney

[toc] | [prev] | [next] | [standalone]

#4434

>> > Look at the big two sites for open-source repositories -- github and
>> > bitbucket.
> Note that there are three: Launchpad (backed by Bazaar) is the other
> “big site” for free-software project hosting.

There is also patch-tag.com (using darcs) though it is smaller.

[toc] | [prev] | [next] | [standalone]

#4426

On Sunday 01 May 2011 18:11, Dietmar Schwertberger wrote:

> Am 01.05.2011 02:47, schrieb Shawn Milochik:
>> Look at the big two sites for open-source repositories -- github and
>> bitbucket. One's git, the other Mercurial. I don't think you can go
>> wrong picking either one.
> 
> Can any of those be used from Python as a library, i.e. something like
> import Hg
> r = Hg.open(path)
> 
> When I had a look at Mercurial, which is implemented in Python,
> it was implemented in a way that I could not do that. It was implemented
> as rather monolithic program which could be used from os.system(...)
> only.

After noting the warnings it contains, see the following page for a
description of the Python API for Mercurial:

  http://mercurial.selenic.com/wiki/MercurialApi

Git also has a Python API, which is fairly reasonable to use, though a bit
different to the Mercurial one:

  http://www.samba.org/~jelmer/dulwich/

I've used both with some success.

David

[toc] | [prev] | [next] | [standalone]

#4490

Am 02.05.2011 01:33, schrieb David Boddie:
> After noting the warnings it contains, see the following page for a
> description of the Python API for Mercurial:
>
>    http://mercurial.selenic.com/wiki/MercurialApi
Ah, yes, no need to use os.sytem(), but all in all not much difference
from doing so (and usage of CLI is recommended instead of using the
API).
I had a look at this page in 2009 and came to the conclusion that it's
no good idea to use Mercurial as library. Seems that this still holds
true.

> Git also has a Python API, which is fairly reasonable to use, though a bit
> different to the Mercurial one:
>
>    http://www.samba.org/~jelmer/dulwich/
That looks more promising to me.
I think I will try this and Bazaar to find which fits my needs better.


Regards,

Dietmar

[toc] | [prev] | [next] | [standalone]

Page 2 of 5 — ← Prev page 1 [2] 3 4 5  Next page →

Back to top | Article view | comp.lang.python

csiph-web