Ebuild for python-mocker, a Python module for mock objects (used for unit tests). Reproducible: Always Steps to Reproduce:
Created attachment 147047 [details] python-mocker-0.10.1.ebuild
why call this "python-mocker"? it should just be called "mocker", i think.
I feel that 'mocker' is a bit too general name for a specifically Python library. There are mock object libraries for just about any object-oriented language. I like it when package names are non-ambiguous.
Not that this would be in the dev/python category. You don't name the ant package "java-ant", but "dev-java/ant". There is "dev-util/git" and not "dev-util/git-the-version-tracker". Simple is better, IMHO. It also makes the ebuild simpler. ;-)
Created attachment 155063 [details] mocker-0.10.1.ebuild Here is my version. What changed: = simplified (suggested name: dev-python/mocker) - more descriptive DESCRIPTION :-) - corrected LICENSE, it's not BSD but PSF-2.2, as the webpage says "Mocker is available under the same license as Python itself"
(In reply to comment #5) > Created an attachment (id=155063) [edit] > - corrected LICENSE, it's not BSD but PSF-2.2, as the webpage says "Mocker is > available under the same license as Python itself" Shouldn't it be PSF-2.4 then?
Created attachment 164124 [details] mocker-0.10.1.ebuild - License updated to PSF-2.4 - Description changed to "Mock objects framework for Python"
Added to CVS. I added a src_test that passed 400+ unit tests and used the description from setup.py Thanks for the ebuild, Macjiej and input from everyone.
