• @chrash0
    67•3 months ago

    Users who need to run their application in Python 2 should do so on a platform that offers support for it

    damn go off

    • @TheGrandNagusEnglish
      54•3 months ago

      SyntaxError: Missing parentheses in call to 'print'. Did you mean print("Fine. Fuck y’all.")?

  • Granixo
    12•3 months ago

    What i really look forward to is that the FD41 LXqt spin uses LXqt 2.0

    • @flubba86
      4•3 months ago

      Oh nice. I used lxqt a couple years ago while I was taking a break from KDE Plasma. I liked it, light and fast and simple. I didn’t know v2.0 is coming out, I’m definitely going to try it.

  • AutoTL;DRBEnglish
    9•3 months ago

    This is the best summary I could come up with:

    A change proposal has been filed by Red Hat engineer Miro Hrončok for retiring Python 2.7 within Fedora 41 and to drop packages still depending upon Python 2.

    We do not wish to simply orphan the package, as we are afraid it would not receive proper care if taken by somebody else.

    If there are potential maintainers interested in maintaining Python 2 in Fedora beyond Fedora 41, they can talk to us and demonstrate their ability and will to take care of Python 2 by joining the maintenance early.

    Users who need to run their application in Python 2 should do so on a platform that offers support for it.

    Developers who still need to test their software on Python 2 can use containers with older Fedora releases or unsupported CentOS/RHEL versions."

    The F41 change proposal still needs the approval of the Fedora Engineering and Steering Committee (FESCo), but it will presumably proceed – well, assuming GIMP 3.0 finally releases this summer so as to not block the Python 2.7 removal.

    The original article contains 379 words, the summary contains 171 words. Saved 55%. I’m a bot and I’m open source!

      • @[email protected]
        15•3 months ago

        No way…

        LOL

        I just told a guy that he shouldnt use yum anymore. While he was using dnf all the time.

        • Dran
          12•3 months ago

          Generally the lifecycle with this sort of thing is old_thing becomes an alias to new_thing, and eventually old_thing gets dropped as an alias down the line.

          It’s still decent advice to learn dnf native calls and to update scripts using yum to those native calls.

        • LalSalaamComrade
          11•3 months ago

          Well, you’re not wrong here. It is better to use dnf-related commands. yum as an alias exists to make sure that old server scripts for RHEL remains compatible.