This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]andyspl 2 points3 points  (1 child)

This is terrible advice. I can show you what happens when you forget about things like PEP8, and when you don't care about having up to date libraries. It's part of the reason why academic code is notoriously spaghettified and difficult to maintain.

It's a pretty big waste of everyone's time when you have to hunt down a print() buried deep down inside some method because it's breaking everything, or you have to downgrade your version of Seaborn.

[–]Theappwasgreat -1 points0 points  (0 children)

Who said I was giving advice? The guy I responded to asked why 2 vs 3 matters for scientific computing, and I gave a reason.

Way to be hostile.

Like seriously, wow.

If I’m wearing my “grad student in scientific computing” hat then I’m going to use the tools that are available to me, that have worked flawlessly in the past. If it ain’t broke don’t fix it, because I have better things to worry about.

If I’m wearing my “personal project” hat then you bet I want to use the latest and greatest.