Mock name is duplicate and generic

[GoogleCodeExporter]

This is more a "philosophical" issue, rather than a coding one.

1) "mock" is really a generic name. Look for "mock", and you'll find dozens of 
unrelated results. Search for "python mock", and you'll probably find out info 
about many different python mock frameworks/tookit/libraries... or the *other* 
python mock project (see point 2)

2) the "mock" name was already taken by Fedora Mock, which is a totally 
different tool (it's a chroot-helper for building rpms, in fact) which is 
written - guess it - in Python:

https://fedorahosted.org/mock/

Fedora Mock seems to have started way before this mock ( 2005 vs end of 2007 ). 
They didn't claim a cheeseshop entry because it's a bit out of their scope - it 
requires quite a bit of configuration beyond the python module - , but 
nonetheless this clash makes it difficult to install both projects on the same 
workstation.

Please: let us look for python mock easily by choosing a new name!

Original issue reported on code.google.com by alan.fra...@gmail.com on 11 Aug 2010 at 2:03

[GoogleCodeExporter]

This mock library is well established now and it would be very confusing to 
change it. Existing documentation, links and references all refer to mock. 
Making it more google'able is a worthy goal. Suggestions?

Original comment by fuzzyman on 11 Aug 2010 at 2:11

• Added labels: ****
• Removed labels: ****

[GoogleCodeExporter]

I think there's a lot of confusion. Of course the transition path should be 
considered, but now it's probably better than later on.

Take a look at the result page if i google "python mock":

http://diigo.com/0c8g5

Out of ten results:
- the very first one refers to a totally different, and apparently older, 
project, python-mock.sf.net , which is got the very same name as yours and 
fedora mock.
- The second and the fifth actually refer to your mock.
- The 9th tells us about python-mock package in Debian, but which mock is it? 
I'd say it's the original python-mock that I saw in #1, but it's actually yours.
- all other results - 60% of the total - point to articles on python mock 
frameworks or other python mock frameworks.

I think everybody would benefit from a name shift, with a possible "backward 
compatibility hook" that could be employed to prevent the need of renaming lots 
of modules around. Maybe the 0.7 and 0.8 releases could offer a new name and 
let the module to be imported as well with the old one, and just issue a 
warning, then with 0.9 or so on you could switch to the new one.

Really, I wouldn't bother if I didn't care. But I was driven crazy finding out 
some info about your mock and fedora mock as well - a really low 
signal-to-noise ratio is something awful in the modern internet.

Original comment by alan.fra...@gmail.com on 11 Aug 2010 at 2:37

• Added labels: ****
• Removed labels: ****

[GoogleCodeExporter]

The fedora mock has had a namespace change, which solves that specific problem. 
mock is too well established to consider a name change now. I'm closing this as 
WontFix.

Original comment by fuzzyman on 8 Oct 2011 at 12:17

• Changed state: WontFix
• Added labels: ****
• Removed labels: ****