Ticket #2381 defect new
Twisted CMD box doesn't always work (win32)
|Reported by:||teratorn||Owned by:||teratorn|
Consider a scenario such as:
Install Twisted for Python2.4
This is the way my machine is set up right now, and when I open a Twisted CMD.exe box and type 'trial' I get this:
C:\>trial Traceback (most recent call last): File "C:\Python24\scripts\trial.py", line 23, in <module> from twisted.scripts.trial import run ImportError: No module named twisted.scripts.trial
This is because Python2.5 is associated with .py files. The Twisted CMD box adds .py to PATHEXT in order to make .py files "executable". It also adds Python's scripts directory to your Path.
With that done it allows you to just type 'trial' and have it work. Unfortunately it will always use the system-default Python interpreter. In my case that is Python2.5, but I don't have Twisted for Python2.5 installed so it can't find the module.
It's not obvious to me how we can fix this. Obviously the user expectation is that when they click the Twisted CMD box link for Python2.4 that will give them commands that actually use Python2.4.
I have a few ideas, but I want to think about it some more and try a few things out first. Suggestions welcome.