Build fails due to MarkupSafe alpha version about octoprint-docker

[lachlancresswell]

I'm getting the same build fail too.

EDIT:
Issue is present in the OctoPrint master - Link

[LongLiveCHIEF]

This is interesting. The docker builds automatically clone the latest stable version of Octoprint from github to run builds, and that means that upstream OctoPrint tags aren't pinned/frozen dependencies in builds.

I'm new to Python in this regards for pinning/freezing dependencies, so I'll have to chat with the other members of @OctoPrint/plugin-repository-maintainers on the best approach to this.

[jneilliii]

I know that for my plugins the dependencies are entered in the setup.py file. I assume OctoPrint uses that somehow to run the correct pip commands, etc. I have seen issues relative to different python versions, and you can pin to versions, I just personally have never had a reported example of that being an issue with any of mine. For example, this is what I have in my Bed Level Visualizer plugin.

plugin_requires = ["numpy"]

probably should be

plugin_requires = ["numpy<=1.16.4"]

Since that's the last version to support Python 2.7.

Hopefully that helps you guys a little.

[markusressel]

It works now, thx! 👍