On Donnerstag, 8. November 2007, Sundance wrote:
On Fri, Nov 02, 2007 at 11:57:15AM +0100, Detlev Offenbach wrote:
meanwhile I removed the carantined import completely because it caused
the interactive Python shell to not work at all. Everything entered in
interactive mode i.e. while not
Hi Detlev,
Okay, I can't reproduce the issue you're describing (although I have an
idea what causes it). May I ask you to give me a simple test case and,
if at all possible, a traceback? Thanks!
As for my email, things have been progressing at last, only to see new
hurdles surface, joy. I'll
Hi Sundance,
actually I found a strange behaviour I have to blame the importer for. If a
module inside the quarantined import does a import os.path, that import
fails. That happens even, if the importing module is somewhere down the
import path.
Regards,
Detlev
PS: Your email is still not
Hi Sundance,
thanks for the quarantined import. I'll include it in the eric4.1 development
line. It'll be part of the next snapshot.
Regards,
Detlev
On Dienstag, 9. Oktober 2007, Sundance wrote:
Sundance wrote:
As time allows, yes, with pleasure. No promise about how successful
it's gonna
Sundance wrote:
As time allows, yes, with pleasure. No promise about how successful
it's gonna be, though, seeing as we're talking badass advanced snake
charming here; we'll see how that goes.
... Ookay.
This was even worse than I imagined, but I'm done and, crazily enough,
it seems to
Detlev wrote:
Actually it is not a minor issue. If possible I would try the import
hook approach. Would you take this task?
Hi Detlev,
As time allows, yes, with pleasure. No promise about how successful it's
gonna be, though, seeing as we're talking badass advanced snake
charming here;
Detlev wrote:
Over here it failed to start the debug client because of an
ImportError. It cannot find the file, if the long import is given.
Hi Detlev,
I worked on it over the weekend on a different flavour of Linux, and I
noticed the same issue you do.
Apparently different distros package
On Montag, 1. Oktober 2007, Sundance wrote:
Detlev wrote:
Over here it failed to start the debug client because of an
ImportError. It cannot find the file, if the long import is given.
Hi Detlev,
I worked on it over the weekend on a different flavour of Linux, and I
noticed the same
Detlev wrote:
Your fix doesn't work over here. It seems, that there is more about
it.
Aw crap. :)
What version of Eric is it, running on what version of Python, and
what's the problem: does the fix cause it to not work in a different
way, or does it just fail to fix the problem I reported?
On Freitag, 28. September 2007, Sundance wrote:
Detlev wrote:
Your fix doesn't work over here. It seems, that there is more about
it.
Aw crap. :)
What version of Eric is it, running on what version of Python, and
what's the problem: does the fix cause it to not work in a different
way,
Detlev wrote:
You are right! And here are instructions for fixing it.
Hi Detlev,
Awesome! Thank you for this!
Don't we risk bumping into the very same problem if somebody ever tries
to run something with a DebugConfig module in Eric though?
In that spirit, I think I've found a more robust
On Donnerstag, 27. September 2007, Sundance wrote:
Detlev wrote:
You are right! And here are instructions for fixing it.
Hi Detlev,
Awesome! Thank you for this!
Don't we risk bumping into the very same problem if somebody ever tries
to run something with a DebugConfig module in Eric
Detlev Offenbach wrote:
That is strange. eric puts the path of the executable at sys.path[0]
just before it's own path. Can you check sys.path in your main
routine or just before the failing import?
Hi Detlev,
Thank you for your reply!
I did check sys.path just before the failing import.
On Mittwoch, 26. September 2007, Sundance wrote:
Detlev Offenbach wrote:
That is strange. eric puts the path of the executable at sys.path[0]
just before it's own path. Can you check sys.path in your main
routine or just before the failing import?
Hi Detlev,
Thank you for your reply!
Hi peeps,
I am trying to run a Python/Qt4 project in Eric3. The project has a file
called Config.py. When I try to run the project from the Eric3
interface, it fails, because the line 'import Config' in my code
imports the Config module from Eric3 instead, even though my project
directory
On Dienstag, 25. September 2007, Sundance wrote:
Hi peeps,
I am trying to run a Python/Qt4 project in Eric3. The project has a file
called Config.py. When I try to run the project from the Eric3
interface, it fails, because the line 'import Config' in my code
imports the Config module from
16 matches
Mail list logo
