dmitrey wrote:
Yes, you are right. But I have to do it due to another issue I haven't
solved yet: Python3 imports don't see files from same directory
http://groups.google.com/group/comp.lang.python/browse_thread/thread/9470dbdacc138709#
That's because the syntax for relative imports has ch
On May 7, 11:53 am, Gregory Ewing wrote:
> Chris Rebert wrote:
> > This is because you did `from Point import
> > ...` in file2.py, whereas in file1.py you did `from
> > openopt.kernel.Point import ...`. These 2 different ways of referring
> > to the same module are sufficient to "trick"/"outsmart
Chris Rebert wrote:
This is because you did `from Point import
...` in file2.py, whereas in file1.py you did `from
openopt.kernel.Point import ...`. These 2 different ways of referring
to the same module are sufficient to "trick"/"outsmart" (C)Python and
cause it to import the same module twice
On Fri, May 6, 2011 at 4:20 AM, dmitrey wrote:
> Thanks Cris, however, I had understood reason of the bug and mere
> informed Python developers of the bug to fix it.
No you haven't. Few if any Python developers make a habit of reading
this newsgroup. To actually report the issue so that it migh
ernel.Point import Point
> > p = Point()
>
> > now let's pass p into a func from .../openopt/kernel/file2.py and
> > check
> > from Point import Point
> > isinstance(p, Point)
>
> > So, it returns False!
>
> > p is , while Point is > openopt.kern
p into a func from .../openopt/kernel/file2.py and
> check
> from Point import Point
> isinstance(p, Point)
>
> So, it returns False!
>
> p is , while Point is openopt.kernel.Point.Point at 0x2048e20>
>
> [Subject: seems like a bug in isinstance()]
This is due to a pec
hi all,
suppose I've created a class Point in file .../openopt/kernel/Point.py
Consider the code in file .../somewhere/file1.py
from openopt.kernel.Point import Point
p = Point()
now let's pass p into a func from .../openopt/kernel/file2.py and
check
from Point import Point
isinstance(p, Point)
