GitHub user gyanu2507 added a comment to the discussion: Is it nessessary for using rapper around the java library or we can link all the existing library ?
You do not wrap pymodbus / python-snap7 as the Python baseline. PLC4X generates each language from the same protocol specs (MSPEC). The public API (`PlcDriverManager`, connection strings, request builders) is meant to look the same in Java, Go, C, and Python. Bolting existing Python libraries underneath would fork that API and make a later swap painful, not cheaper. For Python, that generated binding is **PLC4Py**. It is still early: install from the repo, not PyPI, and the drivers that exist today are Modbus and UMAS. Getting started is here: https://plc4x.apache.org/plc4x/latest/users/getting-started/plc4py.html If you need S7 / EtherNet/IP / etc. in production Python **now**, call the Java library (JPype, a small service, or the PLC4X server) or keep pymodbus/python-snap7 for that one protocol. Those libs will not grow into the rest of PLC4X. If you want to help Python ship faster, the useful work is more generated drivers in PLC4Py, not adapters around the ecosystem libs. GitHub link: https://github.com/apache/plc4x/discussions/2740#discussioncomment-18390041 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
