Hello folks,\n\nPygame -\-the best little 2d game engine in Pythoina-\- is great for\nlittle 2d one off games and such (or so i've heard). I really don't do\nmuch 2d graphics but pygame has some other helpful modules so i\ndownloded it about a year or so ago although i had not used it until\ntoday. I just wanted to be ready just incase the 2d bug bit me. So\nrecently I wanted to do some cdrom automation for one of my Tkinter\nscripts and thought... Hey, i finally found a good use for that old\npygame module!\n\nSo with much anticipation i moseyed on over to my site-packages folder\nand dusted off the old pygame module and docs and i was coding away\njust happy as a clam. I had my initialization working well, my\nejections were a breeze, and i even had some boolean testing\nfunctionality all wrapped up nicely. Boy was i on cloud nine! And just\nas i was finishing up the interface class with a "close" method i\nrealized in horror... YOU CAN OPEN THE CD TRAY WITH PYGAME HOWEVER FOR\nSOME CRUEL AND UNJUST REASON YOU CANNOT CLOSE IT! WTF?\n\nYes at this point i realized that without a method to close the cd\ntray my little module was useless. Sure i could drop into my OS\nfunctionality and close the cdtray by first setting up a device handle\nand calling a few underlying Windows functions however i am convinced\nthat this basic functionality should be a part of any cdrom interface.\nWhy would someone create such an interface and leave out such an\nimportant method? Surely this functionality must be available through\nthe SDL API? What gives pygame developers? What gives?