Skip to main content

The ActivePapers Python edition is no longer maintained, because the Python ecosystem is not sufficiently stable to support an infrastructure for reproducible computations:

https://github.com/activepapers/activepapers-python


GitHub - activepapers/activepapers-python: Python edition of ActivePapers

Python edition of ActivePapers. Contribute to activepapers/activepapers-python development by creating an account on GitHub.
GitHub

reshared this

in reply to SReyCoyrehourcq

Yann Büchau :nixos:
Yann Büchau :nixos:
• •
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.
in reply to Yann Büchau :nixos:

Jack Rusher
Jack Rusher
• •
@nobodyinperson @SReyCoyrehourcq 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.
@Yann Büchau :nixos: @SReyCoyrehourcq

reshared this

in reply to Jack Rusher

Francesco P Lovergine
Francesco P Lovergine
• •
@jack @nobodyinperson @SReyCoyrehourcq This is the main reason I avoided using #Python for a production code almost 20 years ago.
The other main reason was the availability at the time of MS-SQL DBD driver in #Perl (well it is a Sybase one, but it is perfectly the same).
People who use all that code base today still thank gosh.
#perl #python @Yann Büchau :nixos: @SReyCoyrehourcq @Jack Rusher
⇧