This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author meatballhat
Recipients eric.araujo, meatballhat, tarek
Date 2010-05-01.17:28:02
SpamBayes Score 9.5923e-06
Marked as misclassified No
Message-id <1272734883.95.0.862774762497.issue8591@psf.upfronthosting.co.za>
In-reply-to
Content
I probably shouldn't have dropped the PEP8 bomb so much as stated that I feel the module could use some updating.  It's my (very much potentially wrong) understanding that `distutils2.mkpkg` isn't considered library code so much as the guts of a script.  

The reason for my concern about `distutils2.mkpkg` goes something like this:

    - it is a new addition to the distutils toolkit
    - if any kind of walkthrough is to be written for using
      distutils, there's a good chance the `mkpkg` script will
      be mentioned
    - curious folks like myself may look at the source code for
      the script
    - said curious folks may either be new to Python or new to
      programming in general
    - I don't want newcomers getting the wrong idea about Python
      coding standards


I should also mention that I have the same concern(s) about everything in the `Demo` tree of CPython :)

Even if `setup.py` files aren't the eventual goal, if they're around for even another 2 years I think the effort is justified. </2cents>
History
Date User Action Args
2010-05-01 17:28:04meatballhatsetrecipients: + meatballhat, tarek, eric.araujo
2010-05-01 17:28:03meatballhatsetmessageid: <1272734883.95.0.862774762497.issue8591@psf.upfronthosting.co.za>
2010-05-01 17:28:02meatballhatlinkissue8591 messages
2010-05-01 17:28:02meatballhatcreate