Re: [Jython-dev] Exposed types not in CoreExposed.includes

[<fwi...@gm...>]

The ast.* cases are oversights (specifically my oversights, I think). I
suspect the other is an oversight as well.

Thanks for finding them!

-Frank

On Aug 26, 2017 05:47, "Jeff Allen" <ja...@fa...> wrote:

> Tinkering with the logic of PyType, I have run across cases where a class
> is annotated @ExposedType but does produce a TypeBuilder when initialised.
> This is because they are not listed in CoreExposed.includes, are not
> processed by the exposer, and therefore are represented by a  PyJavaType
> object.
>
> I am experimenting with using the annotation, rather than static
> initialisation and looking for a builder, as my way to distinguish the two
> cases, and which reveals this discrepancy whe addBuilder is not called.
>
> So far I found: PyNullImporter, org.python.modules.itertools.imap,
> org.python.antlr.ast.SetComp, org.python.antlr.ast.SetComp, PyXRangeIter.
>
> Such cases are just an oversight, not some subtle choice I haven't
> understood, right?
>
> Jeff
>
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Jython-dev mailing list
> Jyt...@li...
> https://lists.sourceforge.net/lists/listinfo/jython-dev
>