Re: Development tools and practices for Pythonistas

2011-05-08 Thread Roy Smith
In article <58a6bb1b-a98e-4c4a-86ea-09e040cb2...@r35g2000prj.googlegroups.com>, snorble 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

Re: Development tools and practices for Pythonistas

2011-05-08 Thread rusi
On Apr 26, 7:39 pm, snorble 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., f

Python packaging (was Development tools and practices for Pythonistas)

2011-05-06 Thread rusi
On May 6, 2:59 pm, Tim Golden wrote: > On 06/05/2011 10:51, Jonathan Hartley wrote: > > > On Apr 26, 3:39 pm, snorble  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 di

Re: Development tools and practices for Pythonistas

2011-05-06 Thread Tim Golden
On 06/05/2011 10:51, Jonathan Hartley wrote: On Apr 26, 3:39 pm, snorble 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

Re: Development tools and practices for Pythonistas

2011-05-06 Thread Jonathan Hartley
On Apr 26, 3:39 pm, snorble 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/ Al

Re: Development tools and practices for Pythonistas

2011-05-05 Thread buck
I use hg for even 50-line standalone python scripts. It's very well suited to these small environments, and scales up nicely. cd /my/working/dir hg init hg add myscript.py hg ci -m 'added myscript' It's that simple, and now hyou can go back if you make a terrible mistake, and you can post it t

Re: Development tools and practices for Pythonistas

2011-05-04 Thread Anssi Saari
rusi writes: >> I actually use rcs in Windows. Needs a little setup, but works great, >> from Emacs VC-mode too. > > Where do you get it? > [What google is showing seems to be about 10-15 years old] As far as I know, RCS hasn't been updated since 5.7 which is about 10 years old now. Linux distri

Re: Development tools and practices for Pythonistas

2011-05-03 Thread rusi
On May 3, 11:19 pm, Anssi Saari wrote: > rusi writes: > > I am a bit surprised that no one has mentioned rcs so far > > Not an option if you are not on a *ix system and not something I am > > specifically recommending. > > I actually use rcs in Windows. Needs a little setup, but works great, > fr

Re: Development tools and practices for Pythonistas

2011-05-03 Thread jacek2v
On May 2, 12:38 pm, Algis Kabaila wrote: > On Monday 02 May 2011 19:09:38 jacek2v wrote: > > > > > > > > > > > On May 2, 9:48 am, Algis Kabaila wrote: > > > On Monday 02 May 2011 17:19:57 rusi wrote: > > > > On May 2, 12:08 pm, Algis Kabaila > > > > wrote: > > > > > Actually, Bazaar is more conv

Re: Development tools and practices for Pythonistas

2011-05-03 Thread Anssi Saari
rusi writes: > I am a bit surprised that no one has mentioned rcs so far > Not an option if you are not on a *ix system and not something I am > specifically recommending. I actually use rcs in Windows. Needs a little setup, but works great, from Emacs VC-mode too. -- http://mail.python.org/mai

Re: Development tools and practices for Pythonistas

2011-05-02 Thread Dietmar Schwertberger
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

Re: Development tools and practices for Pythonistas

2011-05-02 Thread Algis Kabaila
On Monday 02 May 2011 19:09:38 jacek2v wrote: > On May 2, 9:48 am, Algis Kabaila wrote: > > On Monday 02 May 2011 17:19:57 rusi wrote: > > > On May 2, 12:08 pm, Algis Kabaila > > > > wrote: > > > > Actually, Bazaar is more convenient than rcs for a > > > > single user, as the repository can be t

Re: Development tools and practices for Pythonistas

2011-05-02 Thread jacek2v
On May 2, 9:48 am, Algis Kabaila wrote: > On Monday 02 May 2011 17:19:57 rusi wrote: > > > On May 2, 12:08 pm, Algis Kabaila > wrote: > > > Actually, Bazaar is more convenient than rcs for a single > > > user, as the repository can be the working directory (with > > > a "hidden" .bzr directory th

Re: Development tools and practices for Pythonistas

2011-05-02 Thread Algis Kabaila
On Monday 02 May 2011 17:19:57 rusi wrote: > On May 2, 12:08 pm, Algis Kabaila wrote: > > Actually, Bazaar is more convenient than rcs for a single > > user, as the repository can be the working directory (with > > a "hidden" .bzr directory that stores diffs). > > Dont exactly understand... > Is

Re: Development tools and practices for Pythonistas

2011-05-02 Thread rusi
On May 2, 12:08 pm, Algis Kabaila wrote: > > Actually, Bazaar is more convenient than rcs for a single user, > as the repository can be the working directory (with a "hidden" > .bzr directory that stores diffs).   Dont exactly understand... Is it that you want it specifically hidden? Otherwise rc

Re: Development tools and practices for Pythonistas

2011-05-02 Thread Algis Kabaila
On Monday 02 May 2011 13:22:44 Ben Finney wrote: > rusi writes: > > You may want to look at rcs if you are in the space where > > But today, Bazaar or Mercurial fill that role just as well: > quick simple set up, good tool support (yes, even in Emacs > using VC mode), and easy to use for easy thi

Re: Development tools and practices for Pythonistas

2011-05-01 Thread rusi
On May 2, 8:22 am, Ben Finney wrote: > rusi writes: > > You may want to look at rcs if you are in the space where you want: > > -- something better than tarballs > > -- no pretensions beyond single-user, single-machine, (almost)single- > > file usage (ie small scale) > > -- something that integra

Re: Development tools and practices for Pythonistas

2011-05-01 Thread Ben Finney
rusi writes: > You may want to look at rcs if you are in the space where you want: > -- something better than tarballs > -- no pretensions beyond single-user, single-machine, (almost)single- > file usage (ie small scale) > -- something that integrates nicely with emacs I might have agreed ten ye

Re: Development tools and practices for Pythonistas

2011-05-01 Thread rusi
On Apr 30, 8:21 am, CM wrote: > > 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 >

Re: Development tools and practices for Pythonistas

2011-05-01 Thread Paul Rubin
>> > 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. -- http://mail.python.or

Re: Development tools and practices for Pythonistas

2011-05-01 Thread David Boddie
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

Re: Development tools and practices for Pythonistas

2011-05-01 Thread Ben Finney
Dietmar Schwertberger 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 th

Re: Development tools and practices for Pythonistas

2011-05-01 Thread Jason Earl
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

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

2011-05-01 Thread Martin Schöön
On 2011-04-30, Tim Chase 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

Re: Development tools and practices for Pythonistas

2011-05-01 Thread Dietmar Schwertberger
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

Re: Development tools and practices for Pythonistas

2011-04-30 Thread Shawn Milochik
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

Re: Development tools and practices for Pythonistas

2011-04-30 Thread Ben Finney
Roy Smith 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.

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

2011-04-30 Thread Tim Chase
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 ot

Re: Development tools and practices for Pythonistas

2011-04-30 Thread Martin Schöön
On 2011-04-30, Hans Georg Schaathun wrote: > On Fri, 29 Apr 2011 20:21:58 -0700 (PDT), CM > 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

Re: Development tools and practices for Pythonistas

2011-04-30 Thread Hans Georg Schaathun
On Fri, 29 Apr 2011 20:21:58 -0700 (PDT), CM 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 : o

Re: Development tools and practices for Pythonistas

2011-04-29 Thread Roy Smith
In article , CM 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

Re: Development tools and practices for Pythonistas

2011-04-29 Thread Shawn Milochik
Depends on the project, but I'd start with git the time I created the first file in my project. If you're in the habit of committing then you can easily rollback missteps. If you're in the habit of making branches you can experiment without breaking the currently-working code. -- http://mail.

Re: Development tools and practices for Pythonistas

2011-04-29 Thread CM
> 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

Re: Development tools and practices for Pythonistas

2011-04-29 Thread Ben Finney
Hans Georg Schaathun 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 branchi

Re: Development tools and practices for Pythonistas

2011-04-29 Thread Hans Georg Schaathun
On Wed, 27 Apr 2011 14:24:30 +0200, Jean-Michel Pichavant 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 tru

Re: [OT] Comparing VCS tools (was ""Development tools and practices for Pythonistas")

2011-04-29 Thread Daniel Kluev
We were looking for some simple integrated SCM, issue tracker and wiki in our university for software design and software testing courses, and fossil seems to be perfect match, thanks for sharing. -- With best regards, Daniel Kluev -- http://mail.python.org/mailman/listinfo/python-list

Re: [OT] Comparing VCS tools (was ""Development tools and practices for Pythonistas")

2011-04-29 Thread Kevin Walzer
Fossil is another SCM to consider: http://www.fossil-scm.org/ It's written by the author of SQLite, D. Richard Hipp. It's not as well-known as some of the other DCVS's, but the Tcl/Tk language projects have moved their core development to it (http://core.tcl.tk). This is relevant to Python bec

Re: [OT] VCS tools (was "Development tools and practices for Pythonistas")

2011-04-28 Thread Martin Schöön
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. My humble contribution (from my

Re: Development tools and practices for Pythonistas

2011-04-27 Thread Ben Finney
Thomas Rachel writes: > Am 27.04.2011 13:17, schrieb Jean-Michel Pichavant: > > > You're mistaking, SVN is not restricted to solo work. However it's > > more suitable for solo work than git. > > Why? > > I personally found hg much better than svn. That's why I migrated all > my projects. Indeed.

Re: [OT] VCS tools (was "Development tools and practices for Pythonistas")

2011-04-27 Thread Tim Chase
On 04/27/2011 04:24 AM, Jean-Michel Pichavant wrote: 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 fir

Re: Development tools and practices for Pythonistas

2011-04-27 Thread Thomas Rachel
Am 27.04.2011 13:17, schrieb Jean-Michel Pichavant: You're mistaking, SVN is not restricted to solo work. However it's more suitable for solo work than git. Why? I personally found hg much better than svn. That's why I migrated all my projects. Thomas -- http://mail.python.org/mailman/lis

Re: Development tools and practices for Pythonistas

2011-04-27 Thread Jean-Michel Pichavant
Anssi Saari wrote: Jean-Michel Pichavant 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 doi

Re: Development tools and practices for Pythonistas

2011-04-27 Thread Ben Finney
Jean-Michel Pichavant writes: > 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-tie

Re: Development tools and practices for Pythonistas

2011-04-27 Thread Anssi Saari
Jean-Michel Pichavant 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

Re: Development tools and practices for Pythonistas

2011-04-27 Thread Jean-Michel Pichavant
Chris Angelico wrote: On Wed, Apr 27, 2011 at 7:24 PM, Jean-Michel Pichavant wrote: 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. As someone who for years had "nightly backups and r

Re: Development tools and practices for Pythonistas

2011-04-27 Thread Chris Angelico
On Wed, Apr 27, 2011 at 7:24 PM, Jean-Michel Pichavant wrote: > 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. As someone who for years had "nightly backups and renamed files" as his only VC

Re: Development tools and practices for Pythonistas

2011-04-27 Thread Jean-Michel Pichavant
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

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

2011-04-27 Thread rusi
On Apr 27, 11:39 am, Gour-Gadadhara Dasa wrote: > On Tue, 26 Apr 2011 07:39:41 -0700 (PDT) > > snorble 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

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

2011-04-26 Thread Gour-Gadadhara Dasa
On Tue, 26 Apr 2011 07:39:41 -0700 (PDT) snorble 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

Re: Comparing VCS tools (was ""Development tools and practices for Pythonistas")

2011-04-26 Thread alex23
rusi wrote: > What's the facts? Anyone with any experiences on this? No experience, but I'm rather torn over Fossil. On the one hand, it feels like NIH writ large; on the other hand, it's a DVCS with Trac- like features in a standalone executable less than 1MB in size...by the author of sqlite. -

Re: Comparing VCS tools (was ""Development tools and practices for Pythonistas")

2011-04-26 Thread rusi
On Apr 27, 6:44 am, Tim Chase wrote: > On 04/26/2011 01:42 PM, Algis Kabaila wrote: > > > Thomas, have you tried bzr (Bazaar) and if so do you consider hg > > (Mercurial) better? > > > And why is it better?   (bzr is widely used in ubuntu, which is > > my favourite distro at present). > > Each of

Re: [OT] Comparing VCS tools (was ""Development tools and practices for Pythonistas")

2011-04-26 Thread Tim Chase
On 04/26/2011 01:42 PM, Algis Kabaila wrote: Thomas, have you tried bzr (Bazaar) and if so do you consider hg (Mercurial) better? And why is it better? (bzr is widely used in ubuntu, which is my favourite distro at present). Each of the main 3 (bzr, hg, git) have advantages and disadvantage

Re: Development tools and practices for Pythonistas

2011-04-26 Thread Algis Kabaila
On Wednesday 27 April 2011 09:41:53 Ben Finney wrote: > Chris Angelico 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

Re: Development tools and practices for Pythonistas

2011-04-26 Thread Ben Finney
Chris Angelico 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 t

Re: Development tools and practices for Pythonistas

2011-04-26 Thread Thomas Rachel
Am 26.04.2011 20:42, schrieb Algis Kabaila: Thomas, have you tried bzr (Bazaar) and if so do you consider hg (Mercurial) better? I have played around with bzr, but afterwards more with hg which gave me a better beeling (don't know why)... Thomas -- http://mail.python.org/mailman/listinfo/py

Re: Development tools and practices for Pythonistas

2011-04-26 Thread Dan Stromberg
On Tue, Apr 26, 2011 at 11:04 AM, Jean-Michel Pichavant 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/

Re: Development tools and practices for Pythonistas

2011-04-26 Thread Chris Angelico
On Wed, Apr 27, 2011 at 12:39 AM, snorble wrote: > 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. ... The code is > usually out of sync with todo.txt

Re: Development tools and practices for Pythonistas

2011-04-26 Thread Algis Kabaila
On Wednesday 27 April 2011 04:31:19 CM wrote: > > I guess it depends on your project, but that sounds > > needlessly complex and way too tough with a VCS. I'd say > > just don't go there. > > (Whoops, I meant way too tough *without* a VCS, not with) And read your own emails *before* sending them

Re: Development tools and practices for Pythonistas

2011-04-26 Thread Algis Kabaila
On Wednesday 27 April 2011 03:59:25 Thomas Rachel wrote: > Am 26.04.2011 16:39, schrieb snorble: > > When I write a Python app, I have several unorganized > I don't see how these tools will help to get up to date the > way you describe it - but all other issues are well coped > with using a VCS. I

Re: Development tools and practices for Pythonistas

2011-04-26 Thread CM
> I guess it depends on your project, but that sounds needlessly complex > and way too tough with a VCS.  I'd say just don't go there. (Whoops, I meant way too tough *without* a VCS, not with) -- http://mail.python.org/mailman/listinfo/python-list

Re: Development tools and practices for Pythonistas

2011-04-26 Thread CM
On Apr 26, 10:39 am, snorble 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.,

Re: Development tools and practices for Pythonistas

2011-04-26 Thread Thomas Rachel
Am 26.04.2011 16:39, schrieb snorble: 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 g

Re: Development tools and practices for Pythonistas

2011-04-26 Thread Jean-Michel Pichavant
snorble 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), an

Re: Development tools and practices for Pythonistas

2011-04-26 Thread Jayme Proni Filho
When I said to studying two kind of Version Control. It is because I don't know if you are already working with prgramming. So I think it is very important you know how to work both ways of version control system. You don't need to install both. Just read about one and work with other. For applying

Re: Development tools and practices for Pythonistas

2011-04-26 Thread Jayme Proni Filho
That's my Notebook/PC configuration and I'm user of Gentoo and Slackware. * vi (not vim) for C/C++ * Eclipse for Java * Wing IDE Professional (Python Editor); * Django: Best framework for while in my opinion; * tkinter, GTK and Qt; * MySQL, PostgreSQL ; * Rational Rose Modeler (very expensive)(UML:

Re: Development tools and practices for Pythonistas

2011-04-26 Thread Martin P. Hellwig
On 26/04/2011 14:39, snorble wrote: I would strongly advice to get familiar with: - Lint tools (like PyLint) - Refactoring - Source Control Systems (like Mercurial Hg) - Unit Testing with Code Coverage Followed by either writing your own toolset that integrates all of the above or start learnin

Re: Development tools and practices for Pythonistas

2011-04-26 Thread rusi
On Apr 26, 7:39 pm, snorble wrote: > 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, You either dont want version control > But if I ever made something worth releasing, and got a request > like, "I have probl

Development tools and practices for Pythonistas

2011-04-26 Thread snorble
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.tx