On 06/09/2014 09:46 PM, Tim Golden wrote:
On 09/06/2014 23:31, Ethan Furman wrote:
On 06/09/2014 03:21 PM, Josh English wrote:
So this quirk is coming from PyScripter, which is a shame, because I
don't think it's under development, so it won't be fixed.
The nice thing about Python code is
On Saturday, June 7, 2014 1:24:43 PM UTC-7, Tim Golden wrote:
I'm not 100% sure what your scenario is, but you can certainly help
yourself and us by running the same test on the raw interpreter and then
under PyScripter to determine if the behaviour is to do with IDLE or
with Python
On 06/09/2014 03:21 PM, Josh English wrote:
So this quirk is coming from PyScripter, which is a shame, because I don't
think it's under development, so it won't be fixed.
The nice thing about Python code is you can at least fix your copy. :)
--
~Ethan~
--
On 09/06/2014 23:31, Ethan Furman wrote:
On 06/09/2014 03:21 PM, Josh English wrote:
So this quirk is coming from PyScripter, which is a shame, because I
don't think it's under development, so it won't be fixed.
The nice thing about Python code is you can at least fix your copy. :)
IIRC,
On Fri, Jun 6, 2014 at 2:34 PM, Josh English joshua.r.engl...@gmail.com wrote:
I have been using os.startfile(filepath) to launch files I've created in
Python, mostly Excel spreadsheets, text files, or PDFs.
When I run my script from my IDE, the file opens as I expect. But if I go
back to
On 06/06/2014 21:34, Josh English wrote:
I have been using os.startfile(filepath) to launch files I've created
in Python, mostly Excel spreadsheets, text files, or PDFs.
When I run my script from my IDE, the file opens as I expect. But if
I go back to my script and re-run it, the external
I have been using os.startfile(filepath) to launch files I've created in
Python, mostly Excel spreadsheets, text files, or PDFs.
When I run my script from my IDE, the file opens as I expect. But if I go back
to my script and re-run it, the external program (either Excel, Notepad, or
Acrobat
