posit-dev
publish to PyPI as `rsconnect` and `rsconnect-python`
- update makefile to support building wheels with a different package name
- add a script to rewrite the package name in CI
-
uv runis used for this so that the necessarytomldependency is installed without drama
-
☂️ Python Coverage
current status: ✅
Overall Coverage
| Lines | Covered | Coverage | Threshold | Status |
|---|---|---|---|---|
| 5096 | 3828 | 75% | 0% | 🟢 |
New Files
No new covered files...
Modified Files
No covered modified files...
updated for commit:
15b5a09by action🐍
![github-actions[bot] avatar](https://avatars.githubusercontent.com/in/15368?v=4 "Published by a pub.dev verified publisher"){kind=small}
It might be worth reverting from pyproject.toml to setup.py to support this: https://github.com/posit-dev/rsconnect-python/pull/668
It might be worth reverting from
pyproject.tomlto setup.py to support this: #668
PyPA docs suggest pyproject.toml is the way.
It might be worth reverting from
pyproject.tomlto setup.py to support this: #668
Ya, it's just unconventional for the name field in pyproject.toml to be dynamic. I guess publishing the same project under two different names is also unconventional.
Why not stop using rsconnect-python and wholly migrate to rsconnect?
Why not stop using rsconnect-python and wholly migrate to rsconnect?
I think it will make sense to keep both versions on PyPI up to date until we have the opportunity to update the places where the CLI is used.
PR Preview Action v1.6.1 :---: Preview removed because the pull request was closed. 2025-05-28 15:54 UTC
Merging here appears to be blocked because of the test-connect failures and https://github.com/posit-dev/rsconnect-python/issues/649.
matrixing the distributions job caused the branch protection rules to go out of sync (see this discussion); I've disabled just the branch protection rule requiring a passing of the distributions check, which I will re-add if I can get it to pass here or after it merges to main.