ingest vsc-base & vsc-install#2708
Conversation
…nality from easybuild.base.missing
…d.tools.systemtools
…from easybuild.base.missing
|
Some further clarification w.r.t. my motivation to ingest
|
| "vsc-install >= 0.9.19", | ||
| "vsc-base >= 2.5.8", | ||
| ], | ||
| install_requires=['setuptools >= 0.6'], |
There was a problem hiding this comment.
so where are we still using it?
There was a problem hiding this comment.
setuptools is still used for now, yes, that needs more work
|
It's big but I didn't find anything that caught my attention. |
|
|
||
|
|
||
| class LoggedException(Exception): | ||
| """Exception that logs it's message when it is created.""" |
This set of changes basically ingests
vsc-base&vsc-installinto the EasyBuild framework, either by copying the modules from thevsc.utilsnamespace intoeasybuild.base, or by copying the functionality into an existing module in theeasybuild.toolsnamespace.As such, this effectively removes
vsc-baseandvsc-installas dependencies.I tried to only make minimal changes to the code being copied in, this is mostly about making the EasyBuild framework independent from
vsc-base, not about also cleaning up that code. Therefore, any complaints made by Hound CI will be ignored.I did strip out a bunch of code from the
vsc-basemodules that is currently not required by the EasyBuild framework.Once this change is merged, we can start working on making EasyBuild compatible with Python 3.
Note that the target branch here is
4.x(which was forked from the currentdevelopbranch), so these changes will only be included in EasyBuild 4.0.It's quite likely there will be one or more 3.x releases (e.g. 3.8.1, 3.9.0) before 4.0 is released.
The current
developbranch remains the right place for changes that should be included in the next EasyBuild (3.x) release. I'll keep an eye on mergingdevelopinto the4.xbranch on a regular basis.