I may give this a try. Do we only need to change submodule paths in requirements.txt to PyPI packages?

I may give this a try. Do we only need to change submodule paths in requirements.txt to PyPI packages?

Depends. I think for some of them, we need to push the packages to PyPI, which is a little more work.

Packages that should move to PyPi:

• https://github.com/SymbiFlow/symbiflow-rr-graph
• https://github.com/SymbiFlow/python-fpga-interchange
• https://github.com/SymbiFlow/fasm
• https://github.com/SymbiFlow/xc-fasm
• https://github.com/SymbiFlow/python-sdf-timing
• https://github.com/SymbiFlow/python-symbiflow-v2x
• https://github.com/SymbiFlow/vtr-xml-utils
• https://github.com/SymbiFlow/symbiflow-xc-fasm2bels

Documentation is at https://packaging.python.org/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows/

Publishing package distribution releases using GitHub Actions CI/CD workflows — Python Packaging User Guide

secrets.PYPI_TEST_PASSWORD should be available on any public repository for publishing to https://test.pypi.org/legacy/

Once we have it working, secrets.PYPI_PASSWORD can be used to publish to the real PyPi.