Re: packages and projects
Will Kahn-Greene <[email protected]> Sat, 22 Oct 2011 20:26:23 -0400 (EDT)
| Newsgroups | gmane.comp.web.pyblosxom.devel |
|---|---|
| Message-ID | <[email protected]> |
Ok! I'm going to go for the name change. On Wed, 19 Oct 2011, Sebastian Spaeth wrote: > > On Tue, 18 Oct 2011 21:16:58 -0400 (EDT), Will Kahn-Greene wrote: >> 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. > >> 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. > > While #2 looks cleaner to me, I can feel the pain, and I'd say #1 is > fine. > > Sebastian > ------------------------------------------------------------------------------ The demand for IT networking professionals continues to grow, and the demand for specialized networking skills is growing even more rapidly. Take a complimentary Learning@Cisco Self-Assessment and learn about Cisco certifications, training, and career opportunities. http://p.sf.net/sfu/cisco-dev2dev