On November 1, 2015 at 6:45:16 PM, Nick Coghlan (ncogh...@gmail.com) wrote:
> > However, I also think there's one refinement we can make that
> lets us
> drop the need for a copy-and-paste "setup.py", *without* needing
> to
> define a programmatic build system API: let setup.cfg define
> a mo
On 2 November 2015 at 12:45, Nick Coghlan wrote:
> (Note: I'm still traveling, so I'm not fully caught up on all the
> threads, this one just caught my eye)
...
>> We’d only need to pay that cost on the assumption that we don’t have a Wheel
>> cached already right? Either in the machine local cac
Hi,
Thanks for sharing that video, Donald.
In context, I don't think it's fair to characterize the speaker's
perspective as *dangerous*, or of categorically favoring current users over
potential new users. Obviously there are a lot of tradeoffs around backward
compatibility, and no one-sized-fits
(Note: I'm still traveling, so I'm not fully caught up on all the
threads, this one just caught my eye)
On 30 October 2015 at 00:05, Donald Stufft wrote:
> On October 29, 2015 at 6:59:00 PM, Robert Collins (robe...@robertcollins.net)
> wrote:
>> On 30 October 2015 at 11:50, Robert Collins wrote:
On 31 October 2015 at 14:15, Wayne Werner wrote:
> First, do no harm, eh?
I haven't had time to watch it yet so I don't have the full context of
the observation, but that's only true if current users are considered
categorically more important than future users. That's a dangerous
line of thinkin
On 1 November 2015 at 02:08, Barry Warsaw wrote:
> On Oct 29, 2015, at 10:52 PM, Marcus Smith wrote:
>
>>> If python-dev ends up adopting GitLab for the main PEPs repo, then we
>>> should be able to move the whole process there, rather than needing to
>>> maintain a separate copy.
>>>
>>will that
