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 4 of 5 — ← Prev page 1 2 3 [4] 5  Next page →

#4274 — Re: [OT] VCS tools

Martin Schöön <martin.schoon@gmail.com> writes:

> This has been a pretty informative thread so far. Please keep it coming.
> I am a hardware development guy and do very little software development.
> I have been vaguely aware of tools for version control but inspired by
> this thread I have started looking at Mercurial.

After my passionate Bazaar evangelism? :-)

I seriously recommend anyone looking for a modern VCS to give Bazaar a
decent trial. It's the one I've found newcomers learn most easily, and
it's astoundingly flexible as one's needs with it grow.

-- 
 \                             “I'm a born-again atheist.” —Gore Vidal |
  `\                                                                   |
_o__)                                                                  |
Ben Finney

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

#4279 — Re: [OT] VCS tools

On 04/28/2011 04:50 PM, Ben Finney wrote:
>> This has been a pretty informative thread so far. Please keep it coming.
>> I am a hardware development guy and do very little software development.
>> I have been vaguely aware of tools for version control but inspired by
>> this thread I have started looking at Mercurial.
>
> After my passionate Bazaar evangelism? :-)

I must say my takeaway from the thread was (1) check back in on 
Bazaar to see if the speed is better than I remember and (2) 
Fossil, wha? wow!

-tkc

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

#4280 — Re: [OT] VCS tools

On Fri, Apr 29, 2011 at 8:50 AM, Ben Finney <ben+python@benfinney.id.au> wrote:
> Martin Schöön <martin.schoon@gmail.com> writes:
>
> I seriously recommend anyone looking for a modern VCS to give Bazaar a
> decent trial. It's the one I've found newcomers learn most easily, and
> it's astoundingly flexible as one's needs with it grow.
>

When I was deciding what DVCS I should use for personal projects, Bzr
was first thing I tried. It was quite uncomfortable experience after
svn, esp. with branches and merges, working not the way I was
expecting it to.
Mercurial, on the contrary, did exactly what I was expecting it to,
and was overall very easy to learn.

-- 
With best regards,
Daniel Kluev

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

#4302 — Re: [OT] From svn to something else? (was: VCS tools)

Hmmm.  I am still using svn.

How easy and reliable is it to import my svn version history into
one of the three big DVCS-s mentioned here?  

I am fairly happy with svn, but then I use it more as a backup system
and a means to synchronise multiple systems.  Something better would 
not hurt, but loosing the version history would ...

I am particularly interested in git, not because of any qualities it 
may have but because that's what my colleague pushes, and he seems 
to be pushing our students into it, so it would be useful for me to be
familiar with it.

-- 
:-- Hans Georg

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

#4305 — Re: [OT] From svn to something else?

On 04/29/2011 05:07 AM, Hans Georg Schaathun wrote:
> How easy and reliable is it to import my svn version history
> into one of the three big DVCS-s mentioned here?

I'd say that one of the things SVN has going for it is that it's 
the lingua-franca of VCSes, so just about everything (especially 
the 3 big names mentioned in this thread: hg, bzr, git) can talk 
to svn pretty uneventfully.  As a matter of fact, last I checked, 
Django is hosted in SVN, but most of the developers use DVCS 
tools to check in/out from the main repository to their own local 
hg/bzr/git repos, do their work locally (with the option to work 
offline, branch/merge easily, etc), and then push changesets back 
up when they have a patch they're happy with.

-tkc

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

#4313 — Re: [OT] From svn to something else?

On Fri, 29 Apr 2011 06:50:52 -0500, Tim Chase
  <python.list@tim.thechases.com> wrote:
:  I'd say that one of the things SVN has going for it is that it's 
:  the lingua-franca of VCSes, so just about everything (especially 
:  the 3 big names mentioned in this thread: hg, bzr, git) can talk 
:  to svn pretty uneventfully.  As a matter of fact, last I checked, 
:  Django is hosted in SVN, but most of the developers use DVCS 
:  tools to check in/out from the main repository to their own local 
:  hg/bzr/git repos, do their work locally (with the option to work 
:  offline, branch/merge easily, etc), and then push changesets back 
:  up when they have a patch they're happy with.

I am not sure I get the implications right.  Are you suggesting that
I could keep my svn server, switch to a DVCS client, and reap the
benefits?

-- 
:-- Hans Georg

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

#4317 — Re: [OT] From svn to something else?

On 04/29/2011 12:01 PM, Hans Georg Schaathun wrote:
>    <python.list@tim.thechases.com>  wrote:
> :  I'd say that one of the things SVN has going for it is that it's
> :  the lingua-franca of VCSes, so just about everything (especially
> :  the 3 big names mentioned in this thread: hg, bzr, git) can talk
> :  to svn pretty uneventfully.  As a matter of fact, last I checked,
> :  Django is hosted in SVN, but most of the developers use DVCS
> :  tools to check in/out from the main repository to their own local
> :  hg/bzr/git repos, do their work locally (with the option to work
> :  offline, branch/merge easily, etc), and then push changesets back
> :  up when they have a patch they're happy with.
>
> I am not sure I get the implications right.  Are you suggesting that
> I could keep my svn server, switch to a DVCS client, and reap the
> benefits?

Yep...some are plugins while others are stock/native, but you can 
read your fill at

Git:
http://www.kernel.org/pub/software/scm/git/docs/git-svn.html

Mercurial:
http://mercurial.selenic.com/wiki/WorkingWithSubversion

Bazaar:
http://doc.bazaar.canonical.com/plugins/en/svn-plugin.html


-tkc

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

#4309 — Re: [OT] From svn to something else?

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

> How easy and reliable is it to import my svn version history into
> one of the three big DVCS-s mentioned here?

Bazaar's support for Subversion repositories is great (it requires the
‘bzr-svn’ plug-in, of course). Use the ‘svn-import’ subcommand to import
an entire Subversion repository to a Bazaar repository with all branches
and history intact.

-- 
 \        “Your [government] representative owes you, not his industry |
  `\   only, but his judgment; and he betrays, instead of serving you, |
_o__)        if he sacrifices it to your opinion.” —Edmund Burke, 1774 |
Ben Finney

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

#4310 — Re: [OT] From svn to something else?

On Fri, 29 Apr 2011 22:53:47 +1000
Ben Finney <ben+python@benfinney.id.au> wrote:
> Bazaar's support for Subversion repositories is great (it requires the
> ‘bzr-svn’ plug-in, of course). Use the ‘svn-import’ subcommand to import
> an entire Subversion repository to a Bazaar repository with all branches
> and history intact.

Anyone know how to go the other way?  I recently converted all my
projects over to svn from cvs and then took over another project that
uses bzr. I would prefer everything to be in the same system.

-- 
D'Arcy J.M. Cain <darcy@druid.net>         |  Democracy is three wolves
http://www.druid.net/darcy/                |  and a sheep voting on
+1 416 425 1212     (DoD#0082)    (eNTP)   |  what's for dinner.

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

#4319 — Re: [OT] VCS tools

On 2011-04-28, Ben Finney <ben+python@benfinney.id.au> wrote:
> Martin Schöön <martin.schoon@gmail.com> writes:
>
>> This has been a pretty informative thread so far. Please keep it coming.
>> I am a hardware development guy and do very little software development.
>> I have been vaguely aware of tools for version control but inspired by
>> this thread I have started looking at Mercurial.
>
> After my passionate Bazaar evangelism? :-)
>
Before I think as I remember I was quick out of the blocks.

> I seriously recommend anyone looking for a modern VCS to give Bazaar a
> decent trial. It's the one I've found newcomers learn most easily, and
> it's astoundingly flexible as one's needs with it grow.
>
I'll take look but so far I have found Mercurial pretty easy to get to 
grips with. But then I have only done fairly trivial stuff.

/Martin

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

#4086

On Tue, Apr 26, 2011 at 11:04 AM, Jean-Michel Pichavant
<jeanmichel@sequans.com> wrote:
> You can have a look at SVN and bugzilla, they are free SCM & bug tracker
> applications.
> Make sure it's worth the pain though, these tools are not that easy to
> administrate (the usage is pretty simple).

http://trac.edgewall.org/ is purportedly pretty easy to set up - I've
only used it, not set it up.  Trac gives you SVN and an issue tracker.
 It has plugins for other source control systems.

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

#4113 — recommended Emacs mode (was Re: Development tools and practices for Pythonistas)

[Multipart message — attachments visible in raw view] — view raw

On Tue, 26 Apr 2011 07:39:41 -0700 (PDT)
snorble <snorble@hotmail.com> wrote:

> I'm not a Pythonista, but I aspire to be.
> 
> My current tools:
> 
> Python, gvim, OS file system

I'm also starting with Python after abandoning idea to use D for our
desktop GUI application.

We plan to use Python + Qt along with Cython extensions and wrapping
external C library.

I'm interested which Python mode can you recommend for Emacs:

a) python.el

b) python-mode.el or

c) 'new' python.el (https://github.com/fgallina/python.el)

considering our needs above and desire to use IPython running
Emacs-23.2 on FreeBSD?


Sincerely,
Gour

-- 
“In the material world, conceptions of good and bad are
all mental speculations…” (Sri Caitanya Mahaprabhu)

http://atmarama.net | Hlapicina (Croatia) | GPG: 52B5C810

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

#4117 — Re: recommended Emacs mode (was Re: Development tools and practices for Pythonistas)

On Apr 27, 11:39 am, Gour-Gadadhara Dasa <g...@atmarama.net> wrote:
> On Tue, 26 Apr 2011 07:39:41 -0700 (PDT)
>
> snorble <snor...@hotmail.com> wrote:
> > I'm not a Pythonista, but I aspire to be.
>
> > My current tools:
>
> > Python, gvim, OS file system
>
> I'm also starting with Python after abandoning idea to use D for our
> desktop GUI application.
>
> We plan to use Python + Qt along with Cython extensions and wrapping
> external C library.
>
> I'm interested which Python mode can you recommend for Emacs:
>
> a) python.el
>
> b) python-mode.el or

Thats what I use.

>
> c) 'new' python.el (https://github.com/fgallina/python.el)

Looks interesting -- first time I am hearing...

>
> considering our needs above and desire to use IPython running
> Emacs-23.2 on FreeBSD?

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

#4118 — Re: recommended Emacs mode

[Multipart message — attachments visible in raw view] — view raw

On Wed, 27 Apr 2011 00:51:01 -0700 (PDT)
rusi <rustompmody@gmail.com> wrote:


> > b) python-mode.el or
> 
> Thats what I use.

Upon hearing there is some bug in 23.2 branches with this mode, I've
switched to 'emacs-devel' port and will start with this mode as well.

Thanks.


Sincerely,
Gour

-- 
“In the material world, conceptions of good and bad are
all mental speculations…” (Sri Caitanya Mahaprabhu)

http://atmarama.net | Hlapicina (Croatia) | GPG: 52B5C810

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

#4807

On Apr 26, 3:39 pm, snorble <snor...@hotmail.com> wrote:
> I appreciate any advice or guidance anyone has to offer.

The 'Python Project HOWTO' gives good advice in terms of setting up a
new project, what files and directories to create, what to put in
version control, etc:

http://infinitemonkeycorps.net/docs/pph/

Also, where I work we have tried many IDEs, but happily and
productively use GVim and very little else, so don't feel you *have*
to use an IDE.

Best regards,

  Jonathan Hartley

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

#4809

On 06/05/2011 10:51, Jonathan Hartley wrote:
> On Apr 26, 3:39 pm, snorble<snor...@hotmail.com>  wrote:
>> I appreciate any advice or guidance anyone has to offer.
>
> The 'Python Project HOWTO' gives good advice in terms of setting up a
> new project, what files and directories to create, what to put in
> version control, etc:
>
> http://infinitemonkeycorps.net/docs/pph/

I'd forgotten about that. Great resource! Thanks for reminding me...

TJG

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

#4820 — Python packaging (was Development tools and practices for Pythonistas)

On May 6, 2:59 pm, Tim Golden <m...@timgolden.me.uk> wrote:
> On 06/05/2011 10:51, Jonathan Hartley wrote:
>
> > On Apr 26, 3:39 pm, snorble<snor...@hotmail.com>  wrote:
> >> I appreciate any advice or guidance anyone has to offer.
>
> > The 'Python Project HOWTO' gives good advice in terms of setting up a
> > new project, what files and directories to create, what to put in
> > version control, etc:
>
> >http://infinitemonkeycorps.net/docs/pph/
>
> I'd forgotten about that. Great resource! Thanks for reminding me...
>
> TJG

Thanks for that link.

There is one question in this regard that is not covered: package-use
Of course this http://infinitemonkeycorps.net/docs/pph/#id10 is there.
But I am talking of setting up one's python environment.

For example on a linux box how to best optimize using the native
package manager (eg apt/rpm) along with packages from pypi.  And when
one needs to run with multiple pythons how to use virtualenv etc

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

#4947

On Apr 26, 7:39 pm, snorble <snor...@hotmail.com> wrote:
> I'm not a Pythonista, but I aspire to be.
>
> My current tools:
>
> Python, gvim, OS file system
>
> My current practices:
>
> When I write a Python app, I have several unorganized scripts in a
> directory (usually with several named test1.py, test2.py, etc., from
> random ideas I have tested), and maybe a todo.txt file. Then I hack
> away, adding features in a semi-random order. Then I get busy with
> other things. Maybe one week I spend 20 hours on development. The next
> week, no time on development. A few weeks later when I have some time,
> I'm excited to get back to making progress, only to find that I have
> to spend 30-60 minutes figuring out where I left off. The code is
> usually out of sync with todo.txt. I see people who release new
> versions and bug fixes, so I sometimes will create a new directory and
> continue working from that copy, because it seems like the thing to
> do. But if I ever made something worth releasing, and got a request
> like, "I have problems with the 2.0 version. Can you send me the old
> 1.1 version?" I'd be like, "uhhh... let me hunt through my files by
> hand and get back to you in a month". I'm thinking I can do a lot
> better than this.
>
> I am aware of tools like version control systems, bug trackers, and
> things like these, but I'm not really sure if I need them, or how to
> use them properly. I think having some organization to all of this
> would help me to make more consistent progress, and spend less time
> bringing myself up to speed after some time off.
>
> I really like the idea of having a list of features, and tackling
> those features one at a time. I read about people who do this, and
> each new features gets a new minor version number. It sounds very
> organized and clean. But I'm not really sure of the best way to
> achieve this. Mainly I think I just need some recommendations to help
> create a good mental map of what needs to happen, and mapping jargon
> to concepts. Like, "each feature gets its own directory". Or with a
> version control tool, I don't know if a feature maps to a branch, or a
> commit?
>
> I appreciate any advice or guidance anyone has to offer.

Recently saw this: [Disclaimer: Not tried]

http://labs.creativecommons.org/2010/11/10/bridging-public-bugtrackers-and-local-tasklists/

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

#4957

In article 
<58a6bb1b-a98e-4c4a-86ea-09e040cb2d21@r35g2000prj.googlegroups.com>,
 snorble <snorble@hotmail.com> wrote:

> [standard tale of chaotic software development elided]
>
> I am aware of tools like version control systems, bug trackers, and
> things like these, but I'm not really sure if I need them, or how to
> use them properly.

None of this has anything to do with python.  It's all standard software 
engineering stuff that's the same with any language or technology.

Bug trackers are essential for large projects.  For a one-man project, 
it's probably more effort than it's worth.  For the project I'm on now 
(4 developers co-located with the customer), we're using a shared google 
docs spreadsheet for bug tracking.  It's free, low-overhead, and works 
well enough.  For a single person, even that may be more than you need.

On the other hand version control is essential from day zero, even on a 
one-man project.  There's plenty of perfectly good, free, systems out 
there.  The obvious choices are hg, git, and bzr.  Pick one and use it.  
The nice thing about them all is there's no lock-in.  If you decide you 
don't like the one you're using, you can easily convert your entire code 
repository to any of the others without losing anything.

> I really like the idea of having a list of features, and tackling
> those features one at a time.

Yup, that's the core concept of all the agile development processes that 
are all the rage these days.  Sometimes called "release early and often".

> I read about people who do this, and
> each new features gets a new minor version number.

For the project I'm on, we don't even bother with version numbers.  We 
have a main branch which we (try to) keep stable and shippable at all 
times, and push that to production whenever we've completed a feature 
(or bug fix) that the customer needs.  I see we're currently running:

9be3fc6a0e01cf128f63d1af2b19c180fb4eaacb (tip)

Version numbers make more sense with a traditional ("waterfall") type 
process, where you design a bunch of stuff, write the code, go through a 
testing and bug-fixing cycle, and the finally push it out the door.


> I think I just need some recommendations to help
> create a good mental map of what needs to happen, and mapping jargon
> to concepts. Like, "each feature gets its own directory". Or with a
> version control tool, I don't know if a feature maps to a branch, or a
> commit?

Well, start from the premise that you have a main branch which is always 
shippable.  That means the code runs and passes all the tests after 
every single commit to that branch.

Now, when you need to make a change (add a feature or fix a bug), ask 
yourself if the change is small enough that you can do all the work 
required in one day.  If so, then doing it in a single commit on your 
main branch may make sense.  If not, then spin up a development branch, 
do the work there, and when you're satisfied it's shippable, merge it 
onto your main branch.

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

#5077 — Non Programming in python

Sorry for a silly subject change: A better one will be welcome -- cant
think of a name myself.

There is this whole area of python that may be called the non-
programming side of programming:

Is there some central site where all such is put up?
What if any should such a bundle of things be called?

-------------------------------------------------

  | Area             | Tool(s)                |
  |------------------+------------------------|
  | packaging        | distutils, setuptools, |
  |                  | distutils2, distribute |
  |                  | Native tools (eg apt)  |
  | versioning       | hg, git, bzr           |
  | multiple pythons | virtualenv             |
  | ??               | tox                    |
  | testing          | unittest, nose, pytest |
  | build            | scons, make...         |
  | deployment       | fabric                 |

------------------------------
* Primary Development tools/aids

  1. Help
  2. Completion ('intellisense')
  3. Tags (Jumping)
  4. Refactoring
  5. Integration with 'non-programming' above (eg VCSes, packagers
etc)

* Other Development Tools
  - Debugger
  - Profiler
  - Heap Profiler
  - Coverage

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

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

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

csiph-web