You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I encountered the following error when running the neo4j-graphrag-python package in Python 3.11 and above on an Azure virtual environment:
File "/tmp/8dd44716bf8f03e/antenv/lib/python3.12/site-packages/uuid.py", line 138
if not 0 <= time_low < 1<<32L:
^
SyntaxError: invalid decimal literal
This error is caused by using the backport module uuid, which has been part of the standard library since Python 2.5. In the pyproject.toml file, the uuid module is specified on line 37:
My current workaround involves uninstalling the uuid library after deployment. For the Azure App Service web app, we set an app setting called POST_BUILD_COMMAND with the command:
python -m pip uninstall -y uuid
This fixed our issue, but it would be preferable not to have to do this.
Has anyone else encountered this?
The text was updated successfully, but these errors were encountered:
I encountered the following error when running the neo4j-graphrag-python package in Python 3.11 and above on an Azure virtual environment:
This error is caused by using the backport module uuid, which has been part of the standard library since Python 2.5. In the pyproject.toml file, the uuid module is specified on line 37:
neo4j-graphrag-python/pyproject.toml
Line 37 in d7d6674
Since this library only supports Python 3.9 and above, I request that the uuid = "^1.30" dependency be removed from the file.
This Stack Overflow article helped me identify the root cause of the issue:
https://stackoverflow.com/questions/33612977/how-to-use-uuid-lib-with-mod-wsgi#comment55000535_33612977
My current workaround involves uninstalling the uuid library after deployment. For the Azure App Service web app, we set an app setting called POST_BUILD_COMMAND with the command:
python -m pip uninstall -y uuid
This fixed our issue, but it would be preferable not to have to do this.
Has anyone else encountered this?
The text was updated successfully, but these errors were encountered: