You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I do think that there is only one sustainable way to move from perl to python:
we create a new branch and start rewriting a brand new test-suite drive
we test it and make stable and fully functional (note that the perl version took years to become what it is)
we slowly move from perl to python
Now. Even if perl is so obsolete (are you sure? Look https://github.com/Perl and https://www.perl.org/) I see a big problem: who is going to spend hours in rewriting something that is fully working?
At present, I think, there is no priority in converting the working test suite driver from perl to python...
The current driver is rather complex, and, as Andrea wrote, it would take quite some time to convert it. After all, the test suite driver implements some complex logics, similarly to other third party sw like buildbot or alike, and is a sw by itself.
The situation is different instead, if we consider simpler actions like running a few tests for CI purposes... In these cases, having a simple python script that does the job may be convenient (also in terms of how many people can contribute python rather than perl)...
The two things are not incompatible but rather complementary
I do think that there is only one sustainable way to move from perl to python:
Now. Even if perl is so obsolete (are you sure? Look https://github.com/Perl and https://www.perl.org/) I see a big problem: who is going to spend hours in rewriting something that is fully working?
Originally posted by @andreamarini in yambo-code/yambo#96 (comment)
The text was updated successfully, but these errors were encountered: