[Python.NET] anonymous types from bug tracker
brad at fie.us
Sun Apr 22 20:35:10 CEST 2012
If you feel the suggestion is correct I might take a crack at it. If for no other reason than to get my hands dirty. Do you feel the suggestion is correct?
An alternative might be to create a virtual module like say: clr.anonymous, to put them in? Or do we look to IronPython here?
On Apr 22, 2012, at 1:22 PM, Barton <barton at bcdesignswell.com> wrote:
> Indeed, the mailing list gets more attention than the tracker. I do, however, maintain the tracker as often as I am able.
> As the submitter suggests:
> In method GenericUtil.Register(Type t) there is no test for types which t.Namespace is null.
> Simple correction is just check if t.Namespace is null and then don`t process that type.
> I've had this on my list of things to commit to the trunk, but have gotten sidetracked (by, among other things, building up a new Arch Linux system). I will do my best to get to my list as quickly as I can.
> Thank you so very much,
> On 04/22/2012 09:22 AM, Stephen P. Lepisto wrote:
>> Can you provide a simple reproduction case?
>> On 4/21/2012 1:36 PM, Bradley Friedman wrote:
>>> Hi all.
>>> So I ran into what looks like a bug. Someone else logged it on the
>>> sourceforge bug tracker.
>>> I worked around it as the submitter suggests. However, I have two
>>> Firstly, is the bug tracker the right place to deal with these things?
>>> Or is this mailing list the right place. I ask because the referenced
>>> bug doesn't seem to have been looked at all that much.
>>> Second, is the suggested work around the correct course of action?
>>> Should pythonnet ignore anonymous types?
>>> Bradley Friedman
>>> VFX and Animation
>>> Consulting and Technology
>>> brad at fie.us
>>> Python.NET mailing list - PythonDotNet at python.org
> Python.NET mailing list - PythonDotNet at python.org
More information about the PythonDotNet