Choose unique available network ports
Portpicker provides an API to find and return an available network port for an application to bind to. Ideally suited for use from unittests or for test harnesses that launch local servers.
- Developed at devel:languages:python
- Sources inherited from project openSUSE:Factory
-
2
derived packages
- Download package
-
Checkout Package
osc -A https://api.opensuse.org checkout openSUSE:Factory:Rebuild/python-portpicker && cd $_
- Create Badge
Refresh
Refresh
Source Files
Filename | Size | Changed |
---|---|---|
portpicker-1.6.0.tar.gz | 0000025676 25.1 KB | |
python-portpicker.changes | 0000003473 3.39 KB | |
python-portpicker.spec | 0000002254 2.2 KB |
Latest Revision
Ana Guerrero (anag+factory)
accepted
request 1137821
from
Dirk Mueller (dirkmueller)
(revision 7)
- update to 1.6.0: * Resolve an internal source of potential flakiness on the bind/close port * checks when used in active environments by calling `.shutdown()` before `.close()`. * Add `-h` and `--help` text to the command line tool. * The command line interface now defaults to associating the returned port with its parent process PID (usually the calling script) when no argument was given as that makes more sense. * When portpicker is used as a command line tool from a script, if a port is chosen without a portserver it can now be kept bound to a socket by a child process for a user specified timeout. When successful, this helps minimize race conditions as subsequent portpicker CLI invocations within the timeout window cannot choose the same port. * Some pylint based refactorings to portpicker and portpicker\_test. * Drop 3.6 from our CI test matrix and metadata. It probably still works there, but expect our unittests to include 3.7-ism's in the future. We'll *attempt* to avoid modern constructs in portpicker.py itself but zero guarantees. Using an old Python? Use an old portpicker.
Comments 0