RuntimeError

[Stanislasss]

I cannot run in strict mode anymore, getting the following warnings:

INFO:weasyprint.progress:Step 6 - Creating PDF
WARNING:py.warnings:/usr/local/lib/python3.10/site-packages/pydyf/__init__.py:404: DeprecationWarning: transform is deprecated, use set_matrix instead.
  warn(Stream.transform.__doc__, DeprecationWarning)

WARNING:py.warnings:/usr/local/lib/python3.10/site-packages/pydyf/__init__.py:126: DeprecationWarning: color_space is deprecated, use set_color_space instead.
  warn(Stream.color_space.__doc__, DeprecationWarning)

WARNING:py.warnings:/usr/local/lib/python3.10/site-packages/pydyf/__init__.py:399: DeprecationWarning: text_matrix is deprecated, use set_text_matrix instead.
  warn(Stream.text_matrix.__doc__, DeprecationWarning)

Is there a way to fix those warnings?

The versions I am currently using:

[tool.poetry.dependencies]
python = "^3.10"
mkdocs = "^1.6.0"
mkdocs-material = "9.5.25"
mkdocs-with-pdf = "0.9.3"
mkdocs-awesome-pages-plugin = "2.9.1"
weasyprint = "^62.3"

[tool.poetry.dev-dependencies]
boto3 = "^1.27.1"
click = "^8.1.7"
python-gitlab = "^4.1.1"

[build-system]
requires = ["poetry-core>=1.0.0"]
build-backend = "poetry.core.masonry.api"

Thanks for the help.

[kmurphypolygon]

Did you figure this out yet @Stanislasss I'm getting something similar.

[Stanislasss]

Did you figure this out yet @Stanislasss I'm getting something similar.

Unfortunately not. I just removed the strict flag for the moment. Not happy with it, but we needed to continue working meanwhile.

[kmurphypolygon]

thanks, hmm, i got it on build .. so outside of strict .. and it only builds 5 of 437 docs ... i'll let you know if I come up with anything

[kmurphypolygon]

Looks like because of the deprecation it can't deal with certain graphics, so I'm having to remove them to get a decent PDF, but I guess it's workable for now ...

[Thiti517]

Hello!

I believe that the response to issue #157 should also be applicable here.

Oh! Hello @kmurphypolygon :D

[kmurphypolygon]

Hello!

I believe that the response to issue #157 should also be applicable here.

Oh! Hello @kmurphypolygon :D

:wave: