Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[CheeseSucker]

This is just a post to notify you that we now have a coding standard for our python assets:
https://github.com/fifengine/fifengine/wiki/Python-coding-standards

If you have comments on the article, post them here.

[ShaXbee]

Hello,

I'm lurking around Framework development forum for some time and just want to ask if i can adapt python coding guidelines for project I'm working in?

[mvBarracuda]

Sure go ahead, I don't think that anyone would be angry about that. If you're posting them at some public place (wiki, forums, etc.) it would be great if you could add a little note. Something like "these coding standards have been inspired by <link to our python coding standards>".

[ShaXbee]

Thanks. Of course i'll add note about source.

Edit:
Article is here: http://trac.eu07.pl/eu07-spt/wiki/PythonCodingGuidelines

Few possible problems in coding guidelines:

• What about maximal line length? Do you limit it to 79 characters same as in PEP8?
• Your coding guidelines says little about unit tests - how they are implemented? In seperate files or in same file?
• What documentation generator is used? Tags in docstrings aren't explained.

[phoku]

Hi there,

I honestly think you should head over to the PEP008 first.
That's where most of our guidelines were inspired from.

Regarding UnitTests, we have a bit of a problem there as the code in question (mostly) is ...

• The Editor
• The Gui Library

... and those are difficult to test.

As a documentation generator we use epydoc, another great tool is sphinx.
Django uses it - and well it's docs are awesome(1).

Good luck with your project :-)

-phoku

(1) http://docs.djangoproject.com/en/dev/

[ShaXbee]

Hello phoku,

I honestly think you should head over to the PEP008 first.
That's where most of our guidelines were inspired from.

I know the PEP8, but were to lazy to shorten it to one document

As a documentation generator we use epydoc, another great tool is sphinx.
Django uses it - and well it's docs are awesome(1).

It's hard to disagree that sphinx documentation is great but it requires learning Yet Another Markup Languge (RST in this case) apart from Wiki syntax Because ATM most of interfaces are written in C++ we use doxygen. I dont have idea how to document Python wrappers, maybe you can share some thoughts?

Good luck with your project :-)

Thanks, FIFE and PyChan are success stories and encourage me to work on project I hope that i'll find some time for FIFE development too in near future.

[prock]

Thanks, FIFE and PyChan are success stories and encourage me to work on project I hope that i'll find some time for FIFE development too in near future.

I hope so also 

[emilhem]

http://wiki.fifengine.net/Python_coding_standards

Make sure to update the link.
The correct one is: https://github.com/fifengine/fifengine/wiki/Python-coding-standards

[prock]

Thanks for the pointer emilhem.  Link has been updated.