I have 3.7 built on the finally after some manipulation of their tests.

The Python core devs, however, won't fix a bug that would make this simple and easy. The unwillingness of the core dev community to support platforms outside Win/Mac/Linux (or non-gcc/clang/vcc compilers) is one reason I want nothing to do with core Python contributions any longer.


You know who did fix this upstream? Perl devs... Perl works like a dream on a VAX.

@jba @gewt oh dang, that’s a pretty disappointing closure reason.

@fluffy @gewt My experience is that Python core devs are not remotely interested in platforms outside Windows/Mac/Linux (and barely interested in Windows).

I've been insulted on their bug tracker for not understanding C properly (I was reporting a Windows issue) and had bugs dismissed purely because they don't apply to the "Big 3" platforms.

Python is unportable due to lack of upstream cooperation. The core devs were laughed at on stage during PyCon 2017 for their handling of bugs.

@jba everyone makes fun of PHP these days, but I have to wonder how well *it* does on a VAX. I should fire up SIMH and see.

@jba I don't think it's unreasonable that they only want to support IEEE 754 hardware. I suspect that there are a lot more bugs that would show up from code assuming IEEE 754. Perl's been running on such platforms since the early days IIRC.

@freakazoid @jba that viewpoint assumes there will only ever be IEEE-754 floating point math forever. I understand, but it is also just one more example of CPython not being portable.

@jba Indeed it's not, at least not in the way software used to be. Very little modern software of any complexity is, unfortunately.

Sign in to participate in the conversation
Mastodon @ SDF

"I appreciate SDF but it's a general-purpose server and the name doesn't make it obvious that it's about art." - Eugen Rochko