Conversation

Notices

1. Embed this notice
   powersoffour (powersoffour@mastodon.social)'s status on Friday, 15-Mar-2024 02:02:15 JST powersoffour

   • Clément Robert :python:

   I'm not 100% sure but it might be the case that numpy 2.0 will be a more tricky transition than python 3.0 for us. Part of that is maturity of the project, part of it is the relative depth/breadth of the changes, and part of it is how deeply we rely on it. From what I can tell it has been taking quite a toll on @neutrinoceros who has been Atlas-like in bearing the burden.

   • Embed this notice
     powersoffour (powersoffour@mastodon.social)'s status on Friday, 15-Mar-2024 02:12:00 JST powersoffour

     in reply to

     • Clément Robert :python:

     @neutrinoceros Also, I should totally clarify: numpy 2.0 is awesome! I was venting, but it's not like I haven't both caused *and benefited from* the kind of things that're happening with numpy 2.0. I also probably shouldn't have spoken on behalf of someone else when I really just wanted to highlight how awesome he's been.

   • Embed this notice
     powersoffour (powersoffour@mastodon.social)'s status on Friday, 15-Mar-2024 04:37:34 JST powersoffour

     in reply to

     • Peter Williams

     @pkgw Oh, I meant in terms of disruption to the specific piece of software I work on. I didn't mean global disruption.

   • Embed this notice
     Peter Williams (pkgw@mastodon.world)'s status on Friday, 15-Mar-2024 04:37:35 JST Peter Williams

     in reply to

     @powersoffour I would be seriously "impressed" if the Numpy folks manage to be worse than Python 2>3! 3.0 came out in December 2008 and the Python 2 EOL was January 2020. People don't really talk about it this way but eleven years to make the transition is ... kind of a disaster.