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
As we have now possibility to use python setup.py develop (#145) for build all necessary things via setup.py, can we remove this files?
If this files contain some feature like building in debugging mode or running tests for backend then we could move this features to setup.py script too.
Sometimes developers think that this files are reference of how dpCtl is built. It leads to wrong understanding of dpCtl build procedure.
@PokhodenkoSA Currently the only thing extra the scripts at least on linux is a way to run the test suite for Python and Ctest. I think everything else is there.
If this files contain some feature like building in debugging mode or running tests for backend then we could move this features to setup.py script too.
@PokhodenkoSA I will prefer having at least these two options: debug build and running tests cases, before we remove these scripts.
@oleksandr-pavlyk revisiting the issue after almost a year. All the infrastructure improvements that have happened since then means I have not used these scripts in a very long time. Time to remove them?
In
scripts
folder there are build files for developers but not all developers use it:As we have now possibility to use
python setup.py develop
(#145) for build all necessary things via setup.py, can we remove this files?If this files contain some feature like building in debugging mode or running tests for backend then we could move this features to setup.py script too.
Sometimes developers think that this files are reference of how dpCtl is built. It leads to wrong understanding of dpCtl build procedure.
@diptorupd @reazulhoque @1e-to @vlad-perevezentsev @shssf
The text was updated successfully, but these errors were encountered: