#1934: Some Python programs added to tools/dev
------------------------------+---------------------------------------------
Reporter: mikehh | Owner: jkeenan
Type: cage | Status: assigned
Priority: normal | Milestone:
Component: coding_standards | Version: 2.11.0
Severity: medium | Keywords:
Lang: | Patch:
Platform: |
------------------------------+---------------------------------------------
Comment(by plobsing):
Replying to [comment:8 jkeenan]:
> Replying to [comment:4 coke]:
> > These are not required to build parrot. They are merely to help when
trying to use gdb, and are not required even then.
> >
> > There's no problem with these being in tools/dev, though i'd love to
see them commented to describe their function & use. (and passing
codetest, if they're not already.)
>
> Okay, I can live with that.
>
> And, clearly, I spoke to soon, especially with not knowing what's in
''examples/'', as plobsing++ pointed out in another comment.
>
> So that brings us back to mikehh's original concern: ''What coding
standards should be applied to such files?'' My guesses:
>
> 1. Copyright.
>
> 2. Coda -- though I'm not sure what the correct coda would be.
>
> 3. Linelength -- probably the same as applied to Perl 5 files.
>
> Clearly, the tabs thing won't work for Python ;-)
>
> Which others?
The lazy thing to do would be to declare our python codingstd to be PEP8
and put the onus of testing on the python contributors (e.i.: don't bother
rolling our own conformance tests). It is well known, and already has
tools for testing conformance.
I am hardly an experienced python developer, so take my words with the
appropriate amount of salt.
> Thank you very much.
>
> kid51
--
Ticket URL: <https://trac.parrot.org/parrot/ticket/1934#comment:9>
Parrot <https://trac.parrot.org/parrot/>
Parrot Development
_______________________________________________
parrot-tickets mailing list
[email protected]
http://lists.parrot.org/mailman/listinfo/parrot-tickets
