pyModbusTCP-cli 0.4.0a1__tar.gz → 0.4.0a2__tar.gz

pymodbustcp_cli-0.4.0a2/.gitignore

@@ -0,0 +1,26 @@
+# Also read by hatchling (the build backend): these files never go in the sdist or the wheel.
+
+# bytecode
+__pycache__/
+*.py[cod]
+
+# build outputs
+build/
+dist/
+*.egg-info/
+
+# virtual environments
+/venv/
+/.venv/
+
+# editors and OS
+/.idea/
+/.vscode/
+.DS_Store
+
+# local experiments
+/lab/
+
+# Sphinx documentation (built pages and generated help of the tools)
+/docs/_build/
+/docs/_generated/

{pymodbustcp_cli-0.4.0a1 → pymodbustcp_cli-0.4.0a2}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: pyModbusTCP-cli
-Version: 0.4.0a1
+Version: 0.4.0a2
 Summary: Command line tools for pyModbusTCP: Modbus/TCP server, client and Modbus TCP/RTU gateways
 Project-URL: Source, https://github.com/sourceperl/pyModbusTCP
 Project-URL: Issues, https://github.com/sourceperl/pyModbusTCP/issues
@@ -14,7 +14,7 @@ Classifier: Operating System :: OS Independent
 Classifier: Programming Language :: Python :: 3 :: Only
 Classifier: Topic :: System :: Networking
 Requires-Python: >=3.10
-Requires-Dist: pymodbustcp[serial]==0.4.0a1
+Requires-Dist: pymodbustcp[serial]==0.4.0a2
 Description-Content-Type: text/markdown
 
 # pyModbusTCP-cli
@@ -39,19 +39,19 @@ command in the PATH and installs no dependency.
 pipx install pyModbusTCP-cli
 
 # or in a virtual environment, with the library
-pip install "pyModbusTCP[tools]==0.4.0a1"
+pip install "pyModbusTCP[cli]==0.4.0a2"
 ```
 
 **Alpha**: pyModbusTCP-cli is new with pyModbusTCP 0.4.0, only pre-releases exist for now. The commands, their
 options and their output may still change before the final release. Without a version or `--pre`,
-`pip install "pyModbusTCP[tools]"` installs the stable pyModbusTCP 0.3.1, without the tools.
+`pip install "pyModbusTCP[cli]"` installs the stable pyModbusTCP 0.3.1, without the tools.
 
 Without this package, the tools can still be run from the library alone:
 
 ```bash
 python -m pyModbusTCP.tools server --help
 python -m pyModbusTCP.tools client --help
-pip install "pyModbusTCP[serial]==0.4.0a1" # pyserial, only needed by the gateways
+pip install "pyModbusTCP[serial]==0.4.0a2"  # pyserial, only needed by the gateways
 python -m pyModbusTCP.tools tcp2rtu --help
 python -m pyModbusTCP.tools rtu2tcp --help
 ```
@@ -70,7 +70,7 @@ mbtcp-client -p 5020 write-coil 10 on
 # TCP clients of the 192.168.1.0/24 network can read (only) the RTU slaves of /dev/ttyUSB0
 mbtcp-tcp2rtu -H 0.0.0.0 -A 192.168.1.0/24 --read-only -b 19200 --parity E /dev/ttyUSB0
 
-# a RTU master on /dev/ttyUSB0 reads the Modbus/TCP server 192.168.1.10 (gateway is RTU slave 30)
+# an RTU master on /dev/ttyUSB0 reads the Modbus/TCP server 192.168.1.10 (the gateway is the RTU slave 30)
 mbtcp-rtu2tcp -a 30 -H 192.168.1.10 /dev/ttyUSB0
 ```
 
@@ -84,7 +84,9 @@ The server and the TCP to RTU gateway are designed to be safe by default:
 - they listen on `localhost` and on port 5020 by default: use `-H` with the address of the network interface that
   needs it (`0.0.0.0` only if every network of the host is trusted);
 - `-A/--allow` restricts the clients to some IP addresses or networks, `--read-only` refuses every write;
-- the TCP to RTU gateway refuses broadcast requests (unit id 0) unless `--allow-broadcast` is set.
+- the TCP to RTU gateway refuses broadcast requests (unit id 0) unless `--allow-broadcast` is set;
+- `--max-connections-per-host` (default 16) keeps a single client host from taking every connection, and the TCP
+  to RTU gateway shares the serial line between the client hosts (at most 2 pending requests per host).
 
 Port 502 (the standard Modbus/TCP port) is a privileged port on Unix systems. **Never run these commands as root (or
 with sudo) to listen on it.** Give the `CAP_NET_BIND_SERVICE` capability to the Python interpreter of a virtual

{pymodbustcp_cli-0.4.0a1 → pymodbustcp_cli-0.4.0a2}/README.md

@@ -20,19 +20,19 @@ command in the PATH and installs no dependency.
 pipx install pyModbusTCP-cli
 
 # or in a virtual environment, with the library
-pip install "pyModbusTCP[tools]==0.4.0a1"
+pip install "pyModbusTCP[cli]==0.4.0a2"
 ```
 
 **Alpha**: pyModbusTCP-cli is new with pyModbusTCP 0.4.0, only pre-releases exist for now. The commands, their
 options and their output may still change before the final release. Without a version or `--pre`,
-`pip install "pyModbusTCP[tools]"` installs the stable pyModbusTCP 0.3.1, without the tools.
+`pip install "pyModbusTCP[cli]"` installs the stable pyModbusTCP 0.3.1, without the tools.
 
 Without this package, the tools can still be run from the library alone:
 
 ```bash
 python -m pyModbusTCP.tools server --help
 python -m pyModbusTCP.tools client --help
-pip install "pyModbusTCP[serial]==0.4.0a1" # pyserial, only needed by the gateways
+pip install "pyModbusTCP[serial]==0.4.0a2"  # pyserial, only needed by the gateways
 python -m pyModbusTCP.tools tcp2rtu --help
 python -m pyModbusTCP.tools rtu2tcp --help
 ```
@@ -51,7 +51,7 @@ mbtcp-client -p 5020 write-coil 10 on
 # TCP clients of the 192.168.1.0/24 network can read (only) the RTU slaves of /dev/ttyUSB0
 mbtcp-tcp2rtu -H 0.0.0.0 -A 192.168.1.0/24 --read-only -b 19200 --parity E /dev/ttyUSB0
 
-# a RTU master on /dev/ttyUSB0 reads the Modbus/TCP server 192.168.1.10 (gateway is RTU slave 30)
+# an RTU master on /dev/ttyUSB0 reads the Modbus/TCP server 192.168.1.10 (the gateway is the RTU slave 30)
 mbtcp-rtu2tcp -a 30 -H 192.168.1.10 /dev/ttyUSB0
 ```
 
@@ -65,7 +65,9 @@ The server and the TCP to RTU gateway are designed to be safe by default:
 - they listen on `localhost` and on port 5020 by default: use `-H` with the address of the network interface that
   needs it (`0.0.0.0` only if every network of the host is trusted);
 - `-A/--allow` restricts the clients to some IP addresses or networks, `--read-only` refuses every write;
-- the TCP to RTU gateway refuses broadcast requests (unit id 0) unless `--allow-broadcast` is set.
+- the TCP to RTU gateway refuses broadcast requests (unit id 0) unless `--allow-broadcast` is set;
+- `--max-connections-per-host` (default 16) keeps a single client host from taking every connection, and the TCP
+  to RTU gateway shares the serial line between the client hosts (at most 2 pending requests per host).
 
 Port 502 (the standard Modbus/TCP port) is a privileged port on Unix systems. **Never run these commands as root (or
 with sudo) to listen on it.** Give the `CAP_NET_BIND_SERVICE` capability to the Python interpreter of a virtual

{pymodbustcp_cli-0.4.0a1 → pymodbustcp_cli-0.4.0a2}/hatch_build.py

@@ -13,4 +13,4 @@ from hatchling.metadata.plugin.interface import MetadataHookInterface
 class CustomMetadataHook(MetadataHookInterface):
     def update(self, metadata: dict[str, Any]) -> None:
         # the code of the commands is in the library: exactly the same release
-        metadata['dependencies'] = ['pyModbusTCP[serial]==%s' % metadata['version']]
+        metadata['dependencies'] = [f"pyModbusTCP[serial]=={metadata['version']}"]

pymodbustcp_cli-0.4.0a1/.gitignore

@@ -1,14 +0,0 @@
-build/
-dist/
-*.pyc
-*.egg-info/
-
-/.idea/
-/.vscode/
-
-/venv/
-/lab/
-
-# Sphinx documentation (built pages and generated help of the tools)
-/docs/_build/
-/docs/_generated/