Hardcoded python version in script shebang about doxypypy HOT 4 OPEN

Usually I think that's what people want. If they choose to use a different version of Python, they already can do the '/my/special/python doxypypy.py' instead and it'll run using that specific Python version; there's no need to force everyone to type the extra characters. In fact that's how we test against both Python 2 & Python 3.

from doxypypy.

It your show. But a default python2 interpreter combined with developing python3 code is certainly not an edge case. In the uncertainty created by a new tool this took me quite some time, and I guess more than me will run into it

As usual, in hindsight it's obvious. But that's hindsight...

from doxypypy.

That's fair; at minimum the docs should point it out more. Probably they should also explicitly cover its usage within a virtualenv. AFAICT the majority of doxypypy users are in Python 2 land, and I wouldn't be at all surprised if this is even somewhat related to the reasons why most distros are still using Python 2 for their default system Python.

from doxypypy.

I think 5 years later the situation is clear. Remove Python2 support and close this Issue. ;)

Btw: I do not see why I should run doxypypy as a standalone script? So why does I need a shebang in it? Can you give a use-case for this?

I use doxypypy via the py_filter.py script configured to Doxygen.

from doxypypy.