[Python-Dev] zipimport.c broken with implicit namespace packages

[Brett Cannon]

FIrst off, Mike, sorry about the bug. We have unfortunately let zipimport
get into a sorry state that has made no one want to work on the code
anymore. That being said, I opened https://bugs.python.org/issue25711 to
specifically try to fix this issue once and for all and along the way
modernize zipimport by rewriting it from scratch to be more maintainable
(or whatever the module is named in case we break backwards-compatibility).

At this point the best option might be, Mike, if you do a code review for
https://bugs.python.org/issue17633, even if it is simply a LGTM. I will
then personally make sure the approved patch gets checked in for Python 3.6
in case the rewrite of zipimport misses the release.

On Sat, 2 Jan 2016 at 11:35 <mike.romberg at comcast.net> wrote:

>
>   BRIEF INTRODUCTION:  I've been using python since the early 1.X
> releases.  Mostly for application development.  On occasion I've
> contributed bits to the core:
>
> > grep Romberg Misc/ACKS
> Mike Romberg
>
>   I've recently ported a large application to python3 (it started life
> as using 1.1 so it has been a long road for this codebase).  The one
> big killer feature of python3 I'm attempting to use is implicit
> namespace packages.  But they are broken with the zipimport.c module.
>
>
>   It seems that zipimport.c never worked with these as it is
> comparing paths in the form 'a.b.c' to paths in the form 'a/b/c'.  I
> created a patch that fixes this and makes zipimport work exactly the
> same as a standard filesystem import.  I was getting my patch ready to
> submit when I found that this problem has already been reported:
>
> https://bugs.python.org/issue17633
>
>   Is there anything I can do to help fix this issue?  I could polish
> up my patch create test cases and submit them.  But it looks like the
> above patch does the same thing and is in "the process".  But it has
> been "in the process" for three years.  What else needs to be done?
> I'll help if I can.
>
> Mike
> _______________________________________________
> Python-Dev mailing list
> Python-Dev at python.org
> https://mail.python.org/mailman/listinfo/python-dev
> Unsubscribe:
> https://mail.python.org/mailman/options/python-dev/brett%40python.org
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-dev/attachments/20160102/429bb4b6/attachment.html>