Conversation

Notices

1. Embed this notice
   Yann Büchau :nixos: (nobodyinperson@fosstodon.org)'s status on Monday, 05-Feb-2024 21:44:27 JST Yann Büchau :nixos:

   @SReyCoyrehourcq @khinsen It's true that the #Python ecosystem moves quickly and one can not rely on an analysis to still work *exactly the same* in a couple of months when executed with the then-latest versions. But that's not just the case for Python! Relying on backwards-compatibility of any software stack is not enough and a very poor choice in the first place. As suggested in the README, using something like :guix: #guix or :nixos: #nix or at least containers is necessary.

   • clacke likes this.
   • Embed this notice
     Jack Rusher (jack@berlin.social)'s status on Monday, 05-Feb-2024 21:44:49 JST Jack Rusher

     in reply to

     @nobodyinperson @SReyCoyrehourcq @khinsen I have code (including data analytics code) in C, Common Lisp, and scheme that runs exactly the same after 30+ years, Clojure after 15 years, R after 20+ years. The Python ecosystem is almost uniquely awful for backwards compatibility.

     clacke likes this.