Re: newbie added py-pyasyncore and py-pyasynchat

[David Brownlee <abs%absd.org@localhost>]

On Thu, 24 Oct 2024 at 18:48, <oskar%fessel.org@localhost> wrote:
>
> Hej,
>
> > Am 22.10.2024 um 12:22 schrieb oskar%fessel.org@localhost:
> >
> > i just added py-pyasyncore and py-pyasynchat to wip.  those are needed to get fail2ban in its current incarnation running with python >= 312.  Maybe some other pkgsrc-entries might also benefit from that temporary fix.
>
> I just wanted to ask whether it would be okay to flag python versions before 3.12 as incompatible for these packages.
> The thing is, they are compatible with earlier versions in that they build and install just fine, but they actually do nothing, because the standard asyncore and asynchat of those python versions will be used.
>
> Marking the py-pyasync* packages as incompatible as suggested (and currently in wip) means any package using these deprecated funtcions must conditionally depend on one or both of those packages. Which seems fair enough…
>
> So, if anyone has objections against that plan, please speak up.

No objections as such, just a comment/question:

As developers move onto python 3.12 as later is it likely that some
package build files will end up unconditionally depending on
py-pyasyncore and py-pyasynchat, meaning if we make this change it
will require pkgsrc to patch them to remove the dependencies (I know
pyasyncore and pyasynchat are deprecated, but some things always
linger somewhere).

Alternatively allowing them everywhere would add a NOP dependency to
3.11 and earlier, which when pkgsrc moves to python 3.12 and later as
default will become increasingly less relevant - so a "do less now,
need to do less in future" case

Happy either way, as I'm not likely to be doing the patching :-p

David