FIFE Development > Framework development

Python coding standards

<< < (2/2)

ShaXbee:
Hello phoku,


--- Quote from: phoku on October 21, 2009, 10:32:13 am ---I honestly think you should head over to the PEP008 first.
That's where most of our guidelines were inspired from.

--- End quote ---
I know the PEP8, but were to lazy to shorten it to one document :)


--- Quote from: phoku on October 21, 2009, 10:32:13 am ---As a documentation generator we use epydoc, another great tool is sphinx.
Django uses it - and well it's docs are awesome(1).

--- End quote ---
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?


--- Quote from: phoku on October 21, 2009, 10:32:13 am ---Good luck with your project :-)

--- End quote ---
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:

--- Quote from: ShaXbee on October 22, 2009, 07:29:20 am ---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.

--- End quote ---

I hope so also  ;D

emilhem:

--- Quote from: CheeseSucker on September 20, 2009, 05:02:44 pm ---http://wiki.fifengine.net/Python_coding_standards

--- End quote ---
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.

Navigation

[0] Message Index

[*] Previous page

Go to full version