[tutor] example code

R. A. rob@jam.rr.com
Sun, 07 Jan 2001 23:54:30 -0600

Aw, heck, I went ahead and made a starter page:


Rob A.

"R. A." wrote:
> We could also come up with a CGI form people could use to submit code
> (personal info, filename, source code, commentary, etc.) and simplify
> maintenance.  In the meantime, feel free to send any scripts ready to
> post to me privately, or post to the list (as long as it doesn't anger
> the gods and fierce rabbits).
> Also, if anyone has posted a question to the list that they felt they
> really got some great answers to, feel free to put it together and send
> it along.  Just remember to provide the code (well-commented code is
> super fine) along with any notes on how to make it work and who you
> think deserves a little credit.  I'd be happy to get some initial items
> posted while we work out other details.  And remember to let me know if
> you have a site I can link to.
> The whole idea seems useful also as a way to put up example answers to
> FAQs here on the list.  And why not have items such as a ROT-13 encoding
> script right next to it and a few *Stupid XML Tricks* that show people
> how to do things that prove to be simple enough if you happen to already
> know how to do them.
> Rob Andrews
> Remco Gerlich wrote:
> >
> > On Sun, Jan 07, 2001 at 06:18:23PM -0600, Tesla Coil wrote:
> > > On 7 Jan 2001, John Murray wrote:
> > > > Emailing source directly to the site would probably
> > > > be easiest, in view of the small size of most scripts,
> > >
> > > Were the source posted to a list, the site could just
> > > draw directly from it, become a "best of" collection.
> > > Other site maintainers could do the same thing, with
> > > their different idea of what "best of" means.
> >
> > (I've missed most of the previous discussion, I hope my points weren't
> > discussed to death yet).
> >
> > I think that's quite a lot of work for a maintainer. Read the daily posts,
> > judge what is suitable for the site, and turn the post into some sort of
> > format that's usable (like a web page). The sort of job that you might find
> > a volunteer for, but I wouldn't be surprised if it doesn't last for long.
> >
> > Also, there is already the Python snippets archive (although I currently
> > can't locate the URL - recently erased the bookmarks file and Parnassus'
> > find function is bugging). I'm not sure if it's still active. Anyway, any
> > effort from the list should probably be combined with the snippets archive.
> >
> > And then there's a plan I've had in the back of my mind for a while - some
> > people come here and ask the question "I've read the book and the tutorials,
> > what now?". Apparently they don't learn programming just to get some job done
> > or at least with a specific goal in mind. I'd love an archive with case
> > studies, things to do after the tutorials - make a small programs that
> > downloads comics, implement this game, whatever - I don't have ideas right
> > now but it should be possible to think of plenty of things.
> >
> > The site could have an archive of ideas for projects, things that have been
> > done often but that are useful to learn from. And have hints on where to
> > start - you need to do this, this and this, and these modules will probably
> > be useful. And people who have a working implementation can send them in.
> > That would be a useful resource.
> >
> > Of course, I've already spent far too long on my CS study and I'm just
> > starting my final thesis, there is no way I will volunteer for any of this
> > in the next half year or so. I need the self protection.
> >
> > --
> > Remco Gerlich
> >
> > _______________________________________________
> > Tutor maillist  -  Tutor@python.org
> > http://www.python.org/mailman/listinfo/tutor
> --
> Mississippi Python Interest Group
> http://www.lowerstandard.com/python/mspiggie
> _______________________________________________
> Tutor maillist  -  Tutor@python.org
> http://www.python.org/mailman/listinfo/tutor

Mississippi Python Interest Group