[Slackbuilds-users] remove wheel slackbuild

[fourtysixandtwo]

Arnaud's tests backup my findings and why I didn't create a
python2-wheel and suggest the removal of the old wheel slackbuild
sooner rather than later.  It's just not needed and would only cause a
conflict (/usr/bin/wheel) with python3-wheel.  And we don't need more
wxPython-like conflicts!

The other two builds (rencode and pynacl) that have those same
warnings need to be split/renamed, but also build just fine despite
the wheel missing warning. (as mentioned in my PR)

My testing included comparing the build log and packages between no
wheel , old wheel slackbuild, and just python3-wheel installed.  There
is no difference except the warning and functionality tests are
successful.  (except for python2-automat which seems to be broken and
more testing would be moot given Arnaud planning it's removal)

So I suggest removing the 3 commits to "fix wheel dependency" sitting
in Andrew's branch and we remove the old wheel slackbuild.

Cheers

On Sun, Apr 30, 2023 at 10:41 AM Arnaud via SlackBuilds-users
<slackbuilds-users at slackbuilds.org> wrote:
>
> > > With everything switched to python3-wheel, the wheel slackbuild can now be
> > > removed.
> >
> > i'll keep them for a week and remove them if no reports of scripts broken
> >
> > --
> > Willy Sudiarto Raharjo
> >
>
> Well, there's no python2-wheel.
> It looks fine because it seems it mostly is an shell executable, so whatever
> Python version is used should be ok.
>
> But...
>
> python2-automat builds with python3-wheel with this message :
>
> WARNING: The wheel package is not available.
> DEPRECATION: Python 2.7 reached the end of its life on January 1st, 2020. Please
> upgrade your Python as Python 2.7 is no longer maintained. A future version of
> pip will drop support for Python 2.7. More details about Python 2 support in
> pip, can be found at
> https://pip.pypa.io/en/latest/development/release-process/#python-2-support
>
> Which looks like its making a call to pip, but not installing wheel, and not
> seeming to do much.
> The package builds fine.
> Keeping the old wheel package there removes the warning, and the
> python2-Automat package builds... well exactly the same.
> Removing all wheel packages, old and python3-wheel, well, doesn't change
> anything, the warning is there, the package builds fine.
>
> Anyway, this does not seem that big a problem, but I guess we could just drop
> the python3-wheel requirement altogether, since it builds the same.
>
> My whole not very useful point being that we might see some problems with the
> removal of python2 version of wheel.
>
> But...
>
> I don't care, and all python2 packages should be removed, or presenting
> themselves at the morgue soon ^^
>
> But... (again, I know)
>
> A package like python2-automat is used by python2-twisted, itself used by :
> Nevow TaskCoach python2-txaio Parsley txi2p Scrapy python2-orbited sslstrip
> python2-klein txrequests txsocksx graphite-carbon foolscap
>
> Most of which are probable outdated, not really maintained, and might not work
> at all, but will require some work to know what's what, ask for people to update
> and step up as maintainers, or be removed (then I may at last kill
> python2-twisted and be rid of that old stuff).
>
> Cheers :)
>
>         - Yth / Arnaud.
>
> PS : on a side note, problems might appear at a very late time, because the old
> wheel package is not removed by the name change, therefore the python2 wheel
> will stay in many slackware box used by real people, masking any problem that
> might arise.
> So things will break, but I think those things are either already broken, or
> needs to be updated.
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>