[Python-Dev] Workflow PEP proposals are now closed
Nick Coghlan
ncoghlan at gmail.com
Tue Feb 3 13:02:11 CET 2015
On 3 Feb 2015 01:26, "Brett Cannon" <bcannon at gmail.com> wrote:
>>>
>>
>>
>> Is there going to be discussion between the two approaches or should the
PEPs themselves address each other?
>
>
> Since PEPs are meant to act as a record of what was discussed on a topic
then it probably wouldn't hurt to incorporate why your approach is better
than the other one in the PEP itself. We can obviously talk openly here
when you feel the PEP is ready for it.
One key point worth noting is that the addition of Phabricator to Donald's
proposal actually addresses my most critical concerns regarding workflow
lock-in to a proprietary platform. While I'm genuinely unreasonable on that
particular topic in an upstream context, part of my vehemence in the
original thread was due to bleedover from arguments in other contexts that
happened to be running concurrently, so my belated apologies for that.
In my view, this is now a contest between two different proposals where I
think both represent significant improvements over the status quo. I
obviously still prefer mine, though :)
Cheers,
Nick.
>
> _______________________________________________
> Python-Dev mailing list
> Python-Dev at python.org
> https://mail.python.org/mailman/listinfo/python-dev
> Unsubscribe:
https://mail.python.org/mailman/options/python-dev/ncoghlan%40gmail.com
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-dev/attachments/20150203/48beeacb/attachment.html>
More information about the Python-Dev
mailing list