packages and projects

A while back, I (pretty sure it was me) moved things around and put 
PyBlosxom into the package Pyblosxom (upper-case P lower-case b).  That's 
different than the project name which is PyBlosxom.  In the Pyblosxom 
package is a pyblosxom module.  In the pyblosxom module is a PyBlosxom 
class.

Yes, seriously.  The only good thing I can say is that at least there 
isn't a pYbLOSXOM in there, too.

Anyhow, this is already a source of confusion, but the circumstances don't 
come up with enough frequency that I've decided to fix it.  Until now....

The pain of the current situation increases now that I'm moving core 
plugins into the Pyblosxom package (yes--one more round of the hokey pokey 
with the location of the plugins).  Because of this change, it's very 
likely that the confusion will cause problems for users since new users 
will be typing 'Pyblosxom.plugins.ladeedah' over and over again in the 
load_plugins list in their config.py files.

Further, after I make this change to plugins, the pain of changing the 
package name goes up astronomically.  So the time to fix it is now!

I see two options:

1. Change the name of the project from PyBlosxom to Pyblosxom.  Camel case 
is so 90s anyhow.  This makes the package the same as the project name.

Then we change the name of the PyBlosxom class to Pyblosxom and we're all 
set.  This last bit shouldn't be much pain--only the internals really use 
the PyBlosxom class.

2. Change the name of the package from Pyblosxom to pyblosxom or 
PyBlosxom.  This is a ton of pain because it means all plugins have to 
change.


Because I'm pain-averse these days, I'm inclined to go with option 1 and 
change the name of the project to Pyblosxom.

Does anyone object to a name change?

Does anyone have a better solution or something related that we should 
mull over?

/will

------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2d-oct