Home Original page

[Python-Dev] Merging Jython code into standard Lib [was Re: Python Language Summit at PyCon: Agenda]

Antoine Pitrou solipsis at pitrou.net
Thu Feb 28 21:00:23 CET 2013 
On Thu, 28 Feb 2013 11:46:04 -0800
"fwierzbicki at gmail.com" <fwierzbicki at gmail.com> wrote:
> On Thu, Feb 28, 2013 at 11:24 AM, Chris Jerdonek
> <chris.jerdonek at gmail.com> wrote:
> > On Thu, Feb 28, 2013 at 1:30 AM, Antoine Pitrou <solipsis at pitrou.net> wrote:
> >> Le Wed, 27 Feb 2013 11:33:30 -0800,
> >> "fwierzbicki at gmail.com" <fwierzbicki at gmail.com> a écrit :
> >>>
> >>> There are a couple of spots that might be more controversial. For
> >>> example, Jython has a file Lib/zlib.py that implements zlib in terms
> >>> of the existing Java support for zlib. I do wonder if such a file is
> >>> acceptable in CPython's Lib since its 195 lines of code would be
> >>> entirely skipped by CPython.
> >>
> >> That's a bit annoying. How will we know that the code still works, even
> >> though our buildbots don't exercise it?
> >> Also, what happens if the code doesn't work anymore?
> >
> > Agreed on those problems.  Would it be possible to use a design
> > pattern in these cases so the Jython-only code wouldn't need to be
> > part of the CPython repo?  A naive example would be refactoring zlib
> > to allow subclassing in the way that Jython needs, and then Jython
> > could subclass in its own repo.  CPython could have tests to check the
> > subclass "contract" that Jython needs.
> What about a plat-java section to parallel plat-aix4, plat-darwin,
> etc? The analogy being that the Java platform is somewhat analogous to
> being it's own os? And these areas are not active when on other
> operating systems...

IMHO, we should remove the plat-* directories, they are completely
unmaintained, undocumented, and serve no useful purpose.

Regards

Antoine.
More information about the Python-Dev mailing list