Best way to put out a small package for public scrutiny and use?

From: Kenneth McDonald (kenneth.m.mcdonald_at_sbcglobal.net)
Date: 05/31/04 

Date: Mon, 31 May 2004 18:32:28 GMT

I've created a small (and I believe, very useful) package to ease the
creation and use of regular expressions. I'd like to make it available,
(though the first release will be aimed mostly at finalizing
functionality, not at being a polished project.) I don't want to use
SourceForge, as I don't use CVS, and I'm not yet ready (if ever)
to open up my home Subversion server to public access. If this
was just a single file, I'd simply post it in this newsgroup to
start with, but as it incorporates a couple of files, I need to post
the directory somehow. Any thoughts as to the best way to make
this package available?

Thanks,
Ken

Relevant Pages

  • Re: Best way to put out a small package for public scrutiny and use?
    ... > creation and use of regular expressions. ... > was just a single file, I'd simply post it in this newsgroup to ... this code does and put the package there. ...
    (comp.lang.python)
  • Re: macros
    ... No. Gathering them all in one places just means putting the DEFMETHOD ... And then there'll be a whole mess of explicit scoping ... since that "one place" will belong to one package and you'll want to be ... You don't get scoping by putting things into a single file. ...
    (comp.lang.lisp)
  • Package vs. module
    ... Importing a driver module activates that driver. ... The script features provided useful command line functionality. ... package, the driver code is not loaded unless needed. ... This would keep the module as a single file usable from the command line, ...
    (comp.lang.python)
  • Re: Best way to put out a small package for public scrutiny and use?
    ... Kenneth McDonald wrote: ... > I've created a small package to ease the ... > creation and use of regular expressions. ...
    (comp.lang.python)
  • Multiple Classes per File and use (was: OO Perl...)
    ... assertion that multiple classes *may* be coded into a single file. ... I've always put the package declaration first, ...
    (comp.lang.perl.misc)