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
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.
The documentation for
rsconnect-python
has information on how Connect selects a Python version, but not on howrsconnect
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 usingrsconnect deploy...
The section titled Creating a Manifest for Future Deployment alludes to this, but it is no where made explicit:
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.
The text was updated successfully, but these errors were encountered: