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
Firstly, huge thanks for your work on the s5cmd tool and for contributing to the community with such a valuable tool. 🙏
Goal
We're keen on enhancing the accessibility of s5cmd within Python projects. Our aim is to streamline its integration by enabling installation via a simple pip command:
pip install s5cmd
Upon installing the wheel package, we envision an automatic creation of a convenient executable script1, allowing seamless invocation of the underlying s5cmd executable.
Proposed Next Steps
To foster cohesion and prevent fragmentation, we propose the creation of a dedicated project repository, tentatively named peak/s5cmd-python-distributions. This draws inspiration from analogous projects like scikit-build/cmake-python-distributions2 and scikit-build/ninja-python-distributions3.
We're committed to aiding in the setup and maintenance of this infrastructure. With this in place, we can align our project, ImagingDataCommons/idc-index, to become a pure Python wheel, contingent upon the s5cmd project.
The implementation approach mirrors our current practices within our package:
idc_index/s5cmd/init.py: A Python module with a function used as entry point for the launcher script generation.
CMakeLists.txt: CMake configuration for downloading the go executable using URL and SHA specified in s5cmdUrls.cmake.
Furthermore, we propose the implementation of a GitHub workflow, automatically triggered upon each new release of the corresponding go executable. We plan to adapt the bump function from cmake-python-distributions4 for this purpose.
Alternative Project Repository
We are also considering ImagingDataCommons/s5cmd-python-distributions as an alternative home for this project.
Firstly, huge thanks for your work on the s5cmd tool and for contributing to the community with such a valuable tool. 🙏
Goal
We're keen on enhancing the accessibility of s5cmd within Python projects. Our aim is to streamline its integration by enabling installation via a simple pip command:
Upon installing the wheel package, we envision an automatic creation of a convenient executable script1, allowing seamless invocation of the underlying
s5cmd
executable.Proposed Next Steps
To foster cohesion and prevent fragmentation, we propose the creation of a dedicated project repository, tentatively named
peak/s5cmd-python-distributions
. This draws inspiration from analogous projects likescikit-build/cmake-python-distributions
2 andscikit-build/ninja-python-distributions
3.We're committed to aiding in the setup and maintenance of this infrastructure. With this in place, we can align our project,
ImagingDataCommons/idc-index
, to become a pure Python wheel, contingent upon thes5cmd
project.The implementation approach mirrors our current practices within our package:
Furthermore, we propose the implementation of a GitHub workflow, automatically triggered upon each new release of the corresponding
go
executable. We plan to adapt thebump
function fromcmake-python-distributions
4 for this purpose.Alternative Project Repository
We are also considering
ImagingDataCommons/s5cmd-python-distributions
as an alternative home for this project.Background Details
@fedorov is leading the https://github.com/ImagingDataCommons initiative
I (@jcfr) along with @henryiii, @thewtex and many others are developing and maintaining the
cmake
2,ninja
3 andscikit-build-core
5 Python projects.Footnotes
https://packaging.python.org/en/latest/guides/writing-pyproject-toml/#creating-executable-scripts ↩
scikit-build/cmake-python-distributions ↩ ↩2
scikit-build/ninja-python-distributions ↩ ↩2
https://github.com/scikit-build/cmake-python-distributions/blob/30a96f66e3aeea2be72d517d415f2fb19542485f/noxfile.py#L138-L149 ↩
https://scikit-build-core.readthedocs.io/ ↩
The text was updated successfully, but these errors were encountered: