Making class attributes non-case-sensitive?

[Rafe]

Thanks for the COM pointers Matt. I'll definitely look in to these.
Perhaps this will become a non-issue when I use one of these COM
wrappers...


> Anybody who is used to developing at all is going to
> accept that the software is case sensitive.
Case sensitive? Yes. Letting types create hard to debug behaviors that
raise either no exceptions or strange ones? No. This is what I am
trying to add. Protection.


> It still isn't clear to me _why_ you are wrapping this COM object. You
> aren't adding any functionality.
I've actually been able to add a lot of functionality. I just didn't
post the details of how I'm using it because I didn't think it had any
bearing on the original question. I can add a lot of automation and
convention enforcement to the API by wrapping and extending the
applications object-model. If you want me to give some real-world
examples (which would be related to 3D animation production) I
wouldn't mind doing so at all. I was just trying really hard to keep
the question generic (and failed it seems).


Thanks again for sticking with the discussion!

- Rafe


On Oct 15, 4:03 am, Matimus <mccre... at gmail.com> wrote:
> > So is iterating through dir() to force both the members of dir(), and
> > the requested attribute name, to lower case for a comparison, really
> > the easiest way?
>
> > Thanks again for sticking with me. I hope I didn't add to the
> > confusion. What I learn I will of course pass on.
>
> > - Rafe
>
> It still isn't clear to me _why_ you are wrapping this COM object. You
> aren't adding any functionality. If you are using win32com and the TLB
> object you are using has a tlb, then you can generate wrapper classes
> for them automatically using makepy. You can extend those. If you want
> to do it by hand you should be able to just create a class and inherit
> win32com.client.DispatchBaseClass (and object if you want to make it
> new-style). Unless your users are screaming for this feature, or there
> is some technical reason that it is required, then implementing it is
> a waste of time. Anybody who is used to developing at all is going to
> accept that the software is case sensitive.
>
> Matt