Hi Sebastian, Without claiming any divine authority on the matter, I would suggest separating out googledownloader and plyfile into their own EasyConfigs, and keeping the rest of the PyTorch-related extensions in a "PyTorch extensions”-bundle.
It is always a tricky question when to extend more “core” packages and when to make external bundles, but I’ve certainly started to lean towards using bundles more. This usually makes the core packages easier to update and reduces the possible dependency collisions between different extensions, leaving users to make informed choices (via conflicts when required) about what to load. If possible, could you create pull requests via --new-pr for these EasyConfigs? The documentation is fairly straight forward on https://easybuild.readthedocs.io/en/latest/Integration_with_GitHub.html. I know some of my users are looking for PyTorch extensions, so I (and probably many others) would be happy to test and contribute to these EasyConfigs. :-) > On 19 Feb 2020, at 12:57, Sebastian Potthoff <[email protected]> > wrote: > > Hi, > > I have a question concerning PythonBundles/Packages in general and > specifically to an extension of PyTorch: "PyTorch-Geometric". > (https://github.com/rusty1s/pytorch_geometric) > > I created an EC PythonBundle including several PyTorch extension modules > needed for PyTorch-Geometric. However my exts_list also inlcudes > "googledrivedownloader" and "plyfile". Should these extensions better be > installed by separate EasyConfig files? What's the preferred way? > > There already is a PyTorch PythonPackage EC. Instead of creating a new > PythonBundle, should I update the existing EC and add the extensions to this > file? And when do I use the PythonBundle instead of the PythonPackage EB? > > Many thanks for your help > Sebastian > -- Terje Kvernes Head sysadmin Department of Mathematics University of Oslo
