Cleanups and deprecations going forward...

A few backwards-incompatible things I'm thinking of for PyOpenGL 3.0.3+:

  * eliminate the interpretation of numbers as arrays, that is, if you
    pass 3 to a function expecting an array of integers you will get a
    pointer to address 3, rather than a pointer to an array with a
    single value of 3
      o this will make the Python and C APIs look a lot closer, and
        eliminate a common class of issues where someone can't see how
        to pass offsets to modern array functions
  * drop support for Python 2.5 and below
      o to make it easier to do Python 3.x support, e.g. by using except
        Exception as var: syntax throughout

I don't expect either of those is *too* controversial, but I wanted to 
let people know and have a chance to raise issues before I go about 
implementing them (again, post 3.0.2 release).

Have fun,
Mike

-- 
________________________________________________
   Mike C. Fletcher
   Designer, VR Plumber, Coder
   http://www.vrplumber.com
   http://blog.vrplumber.com


------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
PyOpenGL Homepage
http://pyopengl.sourceforge.net