How do I recover Apple's stock python after accidentally deleting it from /System/Library/Frameworks/Python.framework? Is a Snow Leopard restore the only option?

Question

I accidentally and foolishly deleted my COMPLETE folders: /System/Library/Frameworks/Python.framework/Versions/2.5 and /System/Library/Frameworks/Python.framework/Versions/2.6. Almost 10,000 files were trashed, and only three files would not go through. One of them was the 2.5 python executable. So I put this file back to its original location from trash, but it won't execute (probably for a reason - since Python is missing its remaining files).
I have a python.org python2.7 up and running, but my understanding is that Snow Leopard needs its stock apple provided python for the system to function properly.
Is my only to format my hard drive and restore Snow Leopard from scratch?

Answer 1

I'm actually not trying to do anything other than compile a python script for analyzing scientific data. I am a BIOLOGIST and have absolutely no interest in python for the sake of python. I just need to analyze my data. To get there, I need python/numpy/scipy/wxpython/matplotlib and many other things. I don't know why this seems so "suspicious"??? It's a free world - people are allowed to mess with things. It's not like I am threatening Apple - I made a mistake. Plain and simple. What's the big deal???
I was deleting some skeleton files that were leftover from previous versions of programs and libraries. And that's how I ran into the python2.5 and 2.6. I thought - I will never use these pythons again - why do I have 2.5 files still on my system. I thought I was in /Library/Python, but I was actually in /System/Library/Frameworks. By the time I realized I had wiped out the system's python, it was too late - trash was emptied permanently.
I am in no way trying to "experiment" with apple's python. I know apple's python can happily coexist with python.org or macports python.
In general, I get frustrated with trying to run python bioinformatics scripts on my Mac because there is always an issue. It's either that python is running in 64 bit mode and the scripts are too old. Or, the default apple provided gcc screws up. Quite frankly - Apple and Python are not always best friends.
I used to have a multitude of pythons through fink and macports but I wiped them all out and installed python.org's python27. I also switched to github for all my dependencies and libraries.
In the future, I'll just find a Linux machine to run bioinformatics. I love my Mac, but so far, I have had nothing but nightmares with Python and Apple trying to be friends. Linux is so much better for these types of activities. I can even do a Virtualbox Ubuntu on my MBP and take it from there...
For example, many bioinformatics scripts were made with Carbon and require Carbon. But guess what? Apple kept support for 64-bit Cocoa, but only supports 32-bit Carbon. That makes life ****. Why have a 64 bit architecture with no support for it?