Github user holdenk commented on the issue:
https://github.com/apache/spark/pull/15659
@rxin So the release script will generate pip installable packages, they
just aren't published to PyPI at present (so you have to do `wget [xyz] && pip
install foo.tar.gz`). Publishing to PyPI its self after this would be
relatively easy (it's just a matter of registering the package name and having
the artifacts get uploaded).
As for the disruptiveness - what about this is disruptive? Is it the future
changes to publish to PyPI? This part is an almost purely additive change for
the most part and should people encounter challenges with the approach the
existing system can still be used. The eventual changing of the scripts to
publish to PyPI will take some release coordination - but notably that is left
out of this PR for exactly that reason (as someone who isn't a committer that
felt like something that isn't my place to do).
I want to be clear - while this current PR doesn't go all the way through
to publishing to PyPI it does provide artifacts people can reasonably install
with pip - just slightly more manually than once it's on PyPI. Putting this in
terms of the JVM ecosystem one could think of this as similar to going from not
making jars to making & publishing the jars but not yet copying them to maven
central - making & publishing the jars is an important first step which is
usable by real users - albeit not as simple as the eventual final end point.
I know @rgbkrk has been doing a really good job of explaining why this
change isn't disruptive and is important from a Python user point of view so
maybe he can chime in too :)
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
