search

IBMStreams / administration

Umbrella project for the IBMStreams organization. This project will be used for the management of the individual projects within the IBMStreams organization.
Other
19 stars 10 forks source link

Discussion about the need of new repos for toolkit pypackages #139

Closed markheger closed 5 years ago

markheger commented 5 years ago

Currently the python wrapper packages are part of a pypackage branch in the toolkit repo, e.g. streams.messagehub, streamsx.objectstorage, streamsx.inet etc.

Shall we create new repos for the python wrapper packages, like pypi.streamsx? Advantage: The new repo could contain releases (tags) for package versions, independent from the toolkit version. SPL toolkits do not depend on python packages. Python packages can use toolkits installed in cloud (build service).

Proposed new repos:

ghost commented 5 years ago

Yes, this would be a good idea because we could use distinct tags for toolkit releases and Python package releases. Now we see also the toolkit releases in Pypi because the toolkit repos are connected with Pypi.

ddebrunner commented 5 years ago

Yeah, a separate repo is probably better, makes branching easier.

At some point we might have the Python package include a hidden release SPL toolkit, so if the build service does not have the latest one it be supplied, but that would still seem to work with separate repos.

joergboe commented 5 years ago

Yes, the pypi code shall use a separate repository. Between Streams Toolkit repository and python wrapper code, there is no code in common, no description can be used for both. The only link is the mapping of the python mapper release to the required Streams toolkit release.

markheger commented 5 years ago

@schubon

Please create the following repos:

Top level description similar to streamsx.pypi package. Contributors for all repos: anouri, joergboe, RolefH, markheger

schubon commented 5 years ago

Basic setup done. If you need more or discover a problem, just ping me.