#INSTALL PYDOT WINDOWS .EXE#
exe extension troubles are related to the installation method.
Previous discussions (above, and the links from there) indicate that these.
#INSTALL PYDOT WINDOWS CODE#
Nor do I see any proof that the changed code has been tested under different setups. Both basically do away with some older control logic without explaining why that would not be needed for other users anymore. I get the impression that they are merely quick fixes for specific setups. I do not use Windows, so it is difficult for me to evaluate the suggested solutions. I invite both of them to continue the discussion in this issue ( #205). Note that this would result in the function no longer returning. A comment in issue #203 by who recommends changing line 106 in get_executable_extension() to always return.Note that this would render moot the entire if-block that starts two lines above, as well as the get_executable_extension() function defined a few lines above that. Issue #222 by who suggests commenting out line 117 of pydot.py ( program += extension).Two more duplicates of #205 were reported recently, both with a suggestion for a fix: That issue also has some links to other projects confronted with the same problem, so there may be some inspiration for a solution in there as well. bat files: conda-forge/graphviz-feedstock#34. Later, an issue was created upstream asking for a better solution than.
That commit message links to the responsible 'upstream' code in conda-forge/graphviz-feedstock.bat-code discussed in pydot/pydot-ng#52 to pydot/pydot instead ( 8c55fe5). pydot-ng was a fork of pydot, but (as can be seen later on in that same pydot/pydot-ng#52), the pydot repository was transferred to the same maintainer as pydot-ng ( He then archived pydot-ng and added parts of the.bat extension for Graphviz on Anaconda on Windows was mostly discussed in pydot/pydot-ng#52 by and the ever eloquent It mentions some reasons for why "Python users on Windows typically leverage conda rather than pip", so check it out. I don't have the solution, but just wanted to share some information related to this issue that I came across while investigating another issue: Copy of my comments in duplicate issue #210 (bugs in windows and anaconda env):