posit-dev / posit-dev/rsconnect-python
Docs: how does rsconnect choose a Python version
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 37
- Forks
- 28
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 7
Description
The documentation for rsconnect-python has information on how Connect selects a Python version, but not on how rsconnect selects a version when deploying.
I have a vague feeling that the version of Python is decided by the environment from which the command is run - i.e., the first version of Python found on the PATH when using rsconnect deploy...
The section titled Creating a Manifest for Future Deployment alludes to this, but it is no where made explicit:
It will contain the package dependencies from the current Python environment, or from an alternative Python executable specified in the --python option.
https://docs.posit.co/rsconnect-python/#creating-a-manifest-for-future-deployment
I think we (Support, end users) would benefit from making this information explicit.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Read the “Creating a Manifest for Future Deployment” section and the behavior behind rsconnect deploy..., including the --python option. Confirm how the deployment environment selects Python, then document that selection explicitly and clarify how it relates to the manifest guidance.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100