@GrahamcOfBorg build python3Packages.ws4py

what's the motivating reason behind these disables?

@jonringer: specifically this #73927 (comment) from the PR mentioned in the first message.

Edit: so, the intention is to be a bit graceful about the py2 versions. one could of course also leave it and let the message from cherrypy, once deprecated for 2.7, propagate, but eh. I thought explicitness could be nice.

@jonringer: does the explanation make sense or would another approach be better? I was planning to maybe do this for 1-2 more packages.

It does, but I don't see why we have to be pro-active about removing them if they still build and function as expected.

There's certain packages like sage, which still heavily depend on python2 to function.

Unless there's a pressing reason to disable python2 packages, I'm fine with keeping around frozen versions

@jonringer: There is no pressing reason, its just that cherrypy 17x, which is a dependency of the python 2.7 ws4py has been broken for a while, and the PR linked in the initial issue proposes to deprecate the old version. One of the first issues is that black is incompatible. I went a bit deeper, but there were more issues, that's why the proposal.

Closing, because of lack of interest.