Thanks
Dietrich
Il giorno martedì 11 ottobre 2016 11:00:38 UTC+2, Almar Klein ha scritto:
>
> There already is an issue for it. And now wrote it on my personal todo
> list. Might be a few weeks before I get to it though.
>
>
>
> https://github.com/pyzo/pyzo/issues/248
>
>
>
>
>
>
>
>
Ok I see your point. I did the following further tests:
I have the prova.py file containing print(__file__)
and did the following with
~/anaconda3/bin/python
with open("/tmp/prova.py") as f:
code = compile(f.read(), "/tmp/prova.py", 'exec')
exec(code)
and got
/tmp/prova.py in ()
> 1
Sorry I can't be more specific. It doesn't give me any error messages or
anything else - it just fails...
On Tuesday, October 11, 2016 at 10:54:46 AM UTC+1, Almar Klein wrote:
>
> Hi Will,
>
>
>
> That’s a serious problem. Hard to say what the exact problem is though. We
> switched to
Hi Will,
That’s a serious problem. Hard to say what the exact problem is though. We
switched to using PyQt5 for the binaries, maybe we should fall back to PySide...
- Almar
From: wjro...@gmail.com
Sent: 11 October 2016 11:34
To: Pyzo
Subject: [Pyzo] Re: crash on startup 4.3.1
OK I've
OK I've uninstalled 4.3 and reinstalled 4.2.1 and everything is working
fine again...
There is clearly something weird going on, bu I've no idea what... Can
anyone help me?
Thanks
On Tuesday, October 11, 2016 at 10:06:26 AM UTC+1, wjr...@gmail.com wrote:
>
> Hi,
>
> I've just upgraded to
Hi,
I've just upgraded to 4.3.1 from 4.2.1 and there seems to be a problem.
Every time I try and launch the program I get the splash screen, which then
disappears, and then the program closes. I'm running windows 10 - if that
makes any difference...
Any ideas?
Cheers
Will
--
You received
There already is an issue for it. And now wrote it on my personal todo list.
Might be a few weeks before I get to it though.
https://github.com/pyzo/pyzo/issues/248
From: Dietrich Pescoller
Sent: 10 October 2016 14:39
To: Pyzo
Cc: dit...@gmail.com
Subject: Re: [Pyzo] Strange behavior in
> wouldn't it be the best/easiest solution or simply set the __file__ variable
> as the standard behavior?
Well, if you’d first run a file as a script (which would set __file__), and
then run another file (not as a script) then the __file__ would be overwritten,
which would be wrong, IMO;
