Problem with __init__.py in Python3.1

[hidura at gmail.com]

For finnished the subject i resolve the problem using the PEP-328, i was  
using the old kind of imports :s

On Feb 4, 2010 10:10pm, Hidura <hidura at gmail.com> wrote:
> Thanks i middle resolve the problem, and i going to read the PEP-366 i've  
> been read the 328, i will kept informed of the progresses.

> Thanks again for the help


> On Thu, Feb 4, 2010 at 6:47 PM, Ben Finney ben+python at benfinney.id.au>  
> wrote:

> "Gabriel Genellina" gagsl-py2 at yahoo.com.ar> writes:



> > If you directly run a script from inside a package, Python does not

> > know that it belongs to a package, and treats it as a simple, lonely

> > script. In that case, relative imports won't work.




> Which I consider to be a bug. Fortunately, it's already addressed in PEP

> 366 http://www.python.org/dev/peps/pep-0366/>. Unfortunately, it

> involves more hackish boilerplate at the top of the program, and is only

> available in Python 2.6+.



> --

> \ “Ignorance more frequently begets confidence than does |

> `\ knowledge.” —Charles Darwin, _The Descent of Man_, 1871 |

> _o__) |

> Ben Finney


> --

> http://mail.python.org/mailman/listinfo/python-list






> --
> Hidura

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-list/attachments/20100222/44874286/attachment-0001.html>