That said, I've personally contributed pull requests to both pydot and Network (on behalf of pydot).
How to install pydot on windows update#
Is that ok for you? I think it's better than Hack it because it's less brittle and prone to be broken by a future update in conda packages. I submitted a PR to python-graphviz to detect and use conda's Graphviz binaries, so I do could the same for pydot. What would you recommend downstream packages requiring Graphviz (like, say, our multiphysics simulator) do in the meanwhile? Anaconda uses conda-forge feedstocks as their upstream for conda recipes since Anaconda 5.0. Once the conda-forge Graphviz feedstock is sanitized, would backporting those improvements into the official Graphviz package be feasible?
How to install pydot on windows windows#
If Windows compilation is on the table for 2.40, I'd expect the same time again. Last time it took me about three weeks of hard work to compile 2.38 on Linux/macOS and repackage it on Windows. I don't work for Anaconda anymore, so I can't contribute to fix this in my work time. What do you need from the community to get this gangrenous limb amputated? In fact, they agreed with my decision of repacking its binary installer.īesides, there you'll have to contribute your time to build Graphviz on Windows too, so there's no much of a difference here or thanks for chiming in and trying to find a solution to this. I'm saying that we don't have the time to properly build it right now, and that, since a better build system is on its way, it's better for us to wait for it. I'm ok if you say that the conda repo doesn't care about providing a properly built graphviz, which means I can just give up on the main anaconda repo. If not, we'll wait until the next Graphviz release with CMake support is available. I meant that if you want to help us by spending your time on building Graphviz from sources on Windows, then that's very welcome. PR welcome is very different to "this issue is fixed". Sure, we're breaking the pip package, but we also fixed that problem in our end (which is very similar to what Debian/Fedora/Suse, etc do when they decide to modify something for internal reasons). The problem is breaking an existing package by using a hack in conda in a different package. We're providing the same package under the conda ecosystem. Whereas the Python package is pure Python and can be installed perfectly well with pip. We don't have time to properly build it on Windows, sorry. Yes, and installing a properly built graphviz is exactly what conda can do.