On Thu, Feb 28, 2013 at 11:46 AM, fwierzbicki at gmail.com <fwierzbicki at gmail.com> wrote: >> 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... Oh yeah and this does not preclude the zlib refactoring, and again for the record once this gets serious I'd want to help in bringing up a Jython buildbot to track breakage. -Frank
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4