[BEAM-8309] Document SDK 2.16.0 Python dependencies

[soyrice]

Update Python dependencies page for 2.16.0 release

R: @markflyhigh
CC: @rosetn

---

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

• Choose reviewer(s) and mention them in a comment (R: @username).
• Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
• If this contribution is large, please file an Apache Individual Contributor License Agreement.

Post-Commit Tests Status (on master branch)

Lang	SDK	Apex	Dataflow	Flink	Gearpump	Samza	Spark
Go		---	---		---	---
Java
Python		---			---	---
XLang	---	---	---		---	---	---

Pre-Commit Tests Status (on master branch)

---	Java	Python	Go	Website
Non-portable
Portable	---		---	---

See .test-infra/jenkins/README for trigger phrase, status and link of all Jenkins jobs.

[markflyhigh]

@soyrice Can you repopulate this dependency list? Afaik dill is changed to 0.3.0 in this release. Since 2.16 is published, everything is finalized.

+R: @tvalentyn

[aaltay]

(undo approval) I saw Mark's comment. Yes, the dependencies needs to be updated.

[soyrice]

@soyrice Can you repopulate this dependency list? Afaik dill is changed to 0.3.0 in this release. Since 2.16 is published, everything is finalized.

+R: @tvalentyn

Done!

[soyrice]

(undo approval) I saw Mark's comment. Yes, the dependencies needs to be updated.

Done

[aaltay]

LGTM.

@soyrice how did you generate the dependencies? Did you use a script? Should we add release guide with instruction on re-generating this page after releases?

[soyrice]

LGTM.

@soyrice how did you generate the dependencies? Did you use a script? Should we add release guide with instruction on re-generating this page after releases?

Yeah, Melissa wrote a script that the TWs use: https://raw.githubusercontent.com/melap/beam/pydepsscript/website/scripts/generate_py_deps.py

That sounds like a good idea to me. We should definitely add the docs components to the release guide. But these dependencies are also fairly easy to collect manually.