Message11454

Author tkohn
Recipients stefan.richthofer, tkohn, zyasoft
Date 2017-07-01.07:09:37
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1498892978.48.0.922504390328.issue2599@psf.upfronthosting.co.za>
In-reply-to
Content
I just wanted to add that I usually do not use Jython from inside the PowerShell. I only used it so as to reproduce the bug.

Actually, we created a Python IDE that uses Jython from a graphical user interface. This means that Jython is started as part of GUI and not via a terminal/console at all. It is in this setting that we got feedback from users who could not run the scripts anymore. Further testing then showed that the network paths seemed to be the problem.

When we tried to reproduce the problem with Jython from Windows' "cmd", we found that the problem does not occur because "cmd" assigns a drive letter for network drives. This is the only case known to us so far where the problem does not show. I. e. it is not a bug related to the PowerShell but to Windows in general.
History
Date User Action Args
2017-07-01 07:09:38tkohnsetmessageid: <1498892978.48.0.922504390328.issue2599@psf.upfronthosting.co.za>
2017-07-01 07:09:38tkohnsetrecipients: + tkohn, zyasoft, stefan.richthofer
2017-07-01 07:09:38tkohnlinkissue2599 messages
2017-07-01 07:09:37tkohncreate