Automatic Generation of Python Class Files

Chris Mellon arkanes at gmail.com
Mon Oct 22 13:26:01 EDT 2007


On 10/22/07, Sunburned Surveyor <sunburned.surveyor at gmail.com> wrote:
> I was thinking of a way I could make writing Python Class Files a
> little less painful. I was considering a Ptyhon script that read a
> file with a list of property names and method names and then generated
> a skeleton class file.
>
> I was even thinking of automatically generating the shell for doc
> strings and epydoc tags.
>
> Is there existing scripts that do something like this? If not, I will
> try to come up with something. If I'm sucessful I'll release the code
> under the GPL and will report back to the list.
>
> However, I thought I would check here first so that I don't reinvent
> the wheel.
>
> Thanks,
>
> Scott Huey
>

I can't think of a single reason why you would ever want to do this,
since your "list of method and property names" would be just as
verbose as just typing the actual python code.

Auto generated documentation stubs are considered harmful because they
take the place of real documentation.



More information about the Python-list mailing list