Showing content from http://mail.python.org/pipermail/python-dev/attachments/20140514/7ae1d6bf/attachment.html below:
<p dir="ltr">Main problem with rare platform support is not breaking it accidentally, since without buildbots we won't know when it's broken. This is why we don't make any promises.</p>
<div class="gmail_quote">On May 14, 2014 9:02 PM, "Cameron Simpson" <<a href="mailto:cs@zip.com.au">cs@zip.com.au</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On 14May2014 14:45, Brett Cannon <<a href="mailto:bcannon@gmail.com" target="_blank">bcannon@gmail.com</a>> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On Wed May 14 2014 at 10:43:18 AM, Antoine Pitrou <<a href="mailto:solipsis@pitrou.net" target="_blank">solipsis@pitrou.net</a>><br>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On Wed, 14 May 2014 14:20:26 +0000<br>
Brett Cannon <<a href="mailto:bcannon@gmail.com" target="_blank">bcannon@gmail.com</a>> wrote:<br>
> Over the past week or so there have been 2 patches to add support for<br>
> various UNIX OSs. Now I thought we had stopped trying to add new esoteric<br>
> OSs (e.g. I had never heard of MirOS until the patch for it came in),<br>
but I<br>
> can't find a PEP that spells out what it takes to get a platform<br>
supported (<br>
> <a href="http://legacy.python.org/dev/peps/pep-0011/" target="_blank">http://legacy.python.org/dev/<u></u>peps/pep-0011/</a> is about removing platforms,<br>
> not keeping them or adding them unless you are re-adding one which<br>
> apparently just takes a volunteer).<br>
<br>
OTOH you can fix a platform bug without officially supporting it. If<br>
someone files an OpenBSD-specific patch, it may make sense to commit it<br>
even without officially supporting OpenBSD. In practice it all depends<br>
on how intrusive / reasonable the patch is, and whether it is working<br>
around a platform-specific bug rather than a standards-compliant<br>
limitation.<br>
<br>
(we could call those "stochastically supported platforms" :-))<br>
</blockquote>
<br>
Very true, but these patches are all for e.g. configure to recognize a<br>
specific platform by listing them in some constant. Changing code to be<br>
more general I have no issue with since that's just good practice.<br>
</blockquote>
<br>
Recognition of a special platform isn't "full support", just addition of recognition making possible partial support for special cases. Unless that makes for some horrendous recognition decision tree somewhere I would have thought that's a pretty low bar to accept, and worth doing.<br>
<br>
Leaving aside any bug actually fixed, it makes it much easier for someone else to fix a platform specific bug by making a test constant available for turning on whatever special mode/code is wanted.<br>
<br>
More context on the example patch that triggered this query?<br>
<br>
Just 2c,<br>
Cameron Simpson <<a href="mailto:cs@zip.com.au" target="_blank">cs@zip.com.au</a>><br>
______________________________<u></u>_________________<br>
Python-Dev mailing list<br>
<a href="mailto:Python-Dev@python.org" target="_blank">Python-Dev@python.org</a><br>
<a href="https://mail.python.org/mailman/listinfo/python-dev" target="_blank">https://mail.python.org/<u></u>mailman/listinfo/python-dev</a><br>
Unsubscribe: <a href="https://mail.python.org/mailman/options/python-dev/guido%40python.org" target="_blank">https://mail.python.org/<u></u>mailman/options/python-dev/<u></u>guido%40python.org</a><br>
</blockquote></div>
RetroSearch is an open source project built by @garambo
| Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4