On Sun, Apr 5, 2009 at 10:58 PM, Jack diederich <jackd...@gmail.com> wrote:
> On Sun, Apr 5, 2009 at 10:50 PM, <s...@pobox.com> wrote:
>> Barry> Someone asked me at Pycon about stripping out Demos and Tools.
>>
>> Matthias> +1, but please for 2.7 and 3.1 only.
>>
>> Is there a list of other demos or tools which should be deleted? If
>> possible the list should be publicized so that people can pick up external
>> maintenance if desired.
>
> I liked Brett's (Georg's?) half joking idea at sprints. Just delete
> each subdirectory in a separate commit and then wait to see what
> people revert.
>
> -Jack
Jack brought up a good point - this discussion came up during the
sprints, I believe Martin and others had some good arguments to keep
*some* of the demo/... stuff, however I think we all agreed that it
belongs somewhere else; possibly the documentation.
As it is, the demo/... directory only exists in subversion - it's not
installed anywhere. I really do think that most of the contents can
either be deleted, or moved to the docs where it might be of more use
for people in general.
Random thought - what if we made a docs/demos directory, which
contained sub directories ala Demo/... - and added a sphinx extension
which would detect nested directories and zip them up during the
build? This way, you could add a tag in the .rst for the module that
looked like:
.. demos::
multiprocessing.zip
The zip would not be checked in, but created at build time from
Docs/demos/multiprocessing
Just some thoughts. Back to my coffee.
-jesse
_______________________________________________
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
