Testing Pygbag Support before Releasing #185
-
|
I'm working on adding pygbag support to a package I've made, and I'd like to test it in localhost before releasing it, to ensure that my fixes work as expected. However, the "dependencies" metadata downloads the release version from PyPI, which does not have the fixes. Is there a way to specify, such as in the metadata header, to use a local wheel or a TestPyPI version of a dependency? If not, is there any other way to test a prerelease library for compatibility, or do I need to do a quiet release, test, and delete the release if there are issues? Thank you very much. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
|
to test local changes, remove the library from the PEP block of main.py , unpack its wheel next to the test main.py and relaunch pygbag. Later if you edit files you don't need to relaunch but if you add or remove files to the unpacked wheel you must. |
Beta Was this translation helpful? Give feedback.
-
|
Excellent, that works perfectly. Thanks! |
Beta Was this translation helpful? Give feedback.
to test local changes, remove the library from the PEP block of main.py , unpack its wheel next to the test main.py and relaunch pygbag. Later if you edit files you don't need to relaunch but if you add or remove files to the unpacked wheel you must.