py4web 1.20260403.2 is published

[Massimo DiPierro]

py4web 1.20260403.2 is published

it contains some improvements suggested by Claude and some library upgrades to fix vulnerabilities in third party packages.

I know we have a couple of other outstanding issues and will try look at them asap.

Sorry about lack of progress on the wiki but it is on my todo list.

Massimo

[Jacinto Parga]

Thanks!!

I suggest to make a MARKDOWN helper (similar to web2py MARKMIN). 
I think It can be ver y useful.

[Nazywam się Witek]

Hi,
Sorry, I am not a GitHub user.

1/
In pyDAL 20260313.1, there seems to be a bug in handling the python-mssql driver 1.6.0.

For example, the URI:
mssqlpython://xxx:y...@127.0.0.1/zzz?encrypt=no&trust_server_certificate=yes

causes the following error in my case:
RuntimeError: [Microsoft][ODBC Driver 18 for SQL Server][SQL Server]Login failed for user ''.

AI detected that incorrect argument names are being passed:

- self.driver_args["user"] = user
- self.driver_args["password"] = password
+ self.driver_args["UID"] = user
+ self.driver_args["PWD"] = password

Alternatively, using this directly works:

conn = mssql_python.connect(
    server="127.0.0.1",
    database="zzz",
    port=1433,
    UID="xxx",
    PWD="yyy",
    encrypt="no",
    trust_server_certificate="yes",
)

2/
In Py4Web 1.20260403.2, trying to start gunicorn 23+ with a command similar to:

py4web run ... -s gunicorn ....

causes a gunicorn error about an invalid call argument. I am sorry, I am writing this from memory, but the problematic argument was:
reloading=False

I suspect that the entire **kwargs from the method is being passed into the gunicorn parameters.

[Nazywam się Witek]

!

Do not install the mssql-python library in the same environment as pyDAL.
In my tests, mssql-python 1.6.0 caused serious runtime failures. Simply importing the library was enough to trigger the problem, and pyDAL imports it automatically during driver detection.
No actual connection using mssql_python was required. Even when the application used pymssql as the active driver, the mere presence and import of mssql_python led to errors such as:

pybind11::handle::dec_ref()
PyGILState_Check() failure
Fatal Python error
Communication link failure

After uninstalling mssql-python from the environment, so that it was no longer visible to pyDAL, the problem disappeared.

I love Microsoft ;)