[steve@psycho ~]$ sudo yum install python-pygments
Loading "kernel-module" plugin
Loading "installonlyn" plugin
Setting up Install Process
Parsing package install arguments
Resolving Dependencies
--> Running transaction check
---> Package python-pygments.noarch 0:0.8.1-1.fc7 set to be updated

Dependencies Resolved

=============================================================================
 Package                 Arch       Version          Repository        Size 
=============================================================================
Installing:
 python-pygments         noarch     0.8.1-1.fc7      updates           845 k

Transaction Summary
=============================================================================
Install      1 Package(s)         
Update       0 Package(s)         
Remove       0 Package(s)         

Total download size: 845 k
Is this ok [y/N]: y
Downloading Packages:
(1/1): python-pygments-0. 100% |===========| 845 kB    00:01     
Running Transaction Test
Finished Transaction Test
Transaction Test Succeeded
Running Transaction
  Installing: python-pygments              ################## [1/1] 

Installed: python-pygments.noarch 0:0.8.1-1.fc7
Complete!
[steve@psycho ~]$ 

That's not the submitter's problem. You need to bone up on 
some acronyms, or you'll never make a goodJavaProgrammer. 
Here's a quick lesson in what you should do:

Write a thousand different programs using acronyms that start 
with J that do nothing except fuck up the data as it's being 
transmitted between the database and your application. Then, 
you have to write automated tools that also are acronyms that 
start with J and contain the word "Bean" in there somewhere, 
and those exist to generate parts of those previously mentioned 
thousand programs.

Then, write some Swing components that have nothing to do with 
all of this, and call those by almost exactly the same names, so 
that people get confused and can't do a proper Google search for 
documentation. Name an IDE after the Swing components, too.

Finally, call it all "middleware," give it yet ANOTHER name and 
bundle it all together, making sure that everything breaks if you 
don't include fifty different XML configuration files in the proper 
directory hierarchy that changes with each version.

Then when all of this doesn't work for more than one project 
because it's hopelessly complex, do it all over again and call it 
the next greatest revolution in Java middleware.