[Distutils] Handling Case/Normalization Differences

[Nick Coghlan]

On 2 September 2014 12:54, Chris Jerdonek <chris.jerdonek at gmail.com> wrote:
> On Mon, Sep 1, 2014 at 7:15 PM, Donald Stufft <donald at stufft.io> wrote:
>> I already give notice (and discussion, often times even PEPs) for any
>> change
>> that I believe to be breaking. Wanting more is wanting notice on every
>> single change on the off chance someone somewhere might have some
>> dependency on any random implementation detail.
>
> If you don't have a good sense of what changes might break existing
> tools and don't want to notify people, one possibility is to build in
> a delay between committing to the repo and deploying to production.
> Interested folks could monitor commits to the repo -- giving them a
> chance to ask questions and update their tools if necessary.

That will pick up noise from internal or web only changes that don't
affect the programmatic APIs.

Ideally, we'd have an integration environment where tests for pip,
bandersnatch and devpi were all automatically run against pypi commits
before they went live, but that's rather a lot of work to set up.
Until we have such a system, we may continue to see occasional
incidents like this one.

Cheers,
Nick.

-- 
Nick Coghlan   |   ncoghlan at gmail.com   |   Brisbane, Australia