On Thu, May 15, 2008 at 7:37 AM, Mark Hammond <[EMAIL PROTECTED]> wrote:
> Trying to build pywin32 from the trunk, I see:
>
> from distutils.config import PyPIRCCommand
> File "C:\src\python-svn\lib\distutils\config.py", line 8, in
> from ConfigParser import ConfigParser
> ImportError: No module
On Tue, May 6, 2008 at 1:26 PM, Guido van Rossum <[EMAIL PROTECTED]> wrote:
> On Tue, May 6, 2008 at 12:51 AM, Jeroen Ruigrok van der Werven
> <[EMAIL PROTECTED]> wrote:
> > -On [20080505 05:38], Guido van Rossum ([EMAIL PROTECTED]) wrote:
> > > http://code.google.com/p/rietveld/source/browse
On Wed, Apr 9, 2008 at 3:40 PM, Phillip J. Eby <[EMAIL PROTECTED]> wrote:
> That is indeed a problem -- but it's a social one, not a technical
> one. It's trivial for the publisher of an egg to change their
> command line from "setup.py bdist_egg upload" to "setup.py sdist
> bdist_egg upload",
On Sat, Mar 22, 2008 at 10:02 AM, "Martin v. Löwis" <[EMAIL PROTECTED]> wrote:
> > It seems to me that this discussion is being undermined by not
> > acknowledging the many use cases up front. There is no rationale
> > because there are too many tacit rationales.
>
> I honestly, really, cannot i
On Fri, Mar 21, 2008 at 9:31 PM, "Martin v. Löwis" <[EMAIL PROTECTED]> wrote:
> The objections to the PEP remain the same as they were then,
> though: In the requirements, it says "we need", without saying
> why we need. It then goes on saying "we want" (rephrased)
> "to duplicate APT and RPM",
On Wed, Mar 19, 2008 at 6:15 PM, Jeff Rush <[EMAIL PROTECTED]> wrote:
> Frankly I'd like to see setuptools exploded, with those parts of general use
> folded back into the standard library, the creation of a set of
> non-implementation-specific documents of the distribution formats and
> behavi
