Home

Article setup and discussion

Style

• Discussion style where multiple options are discussed? Or rather uniform article explaining how to do things?
• Who is the audience? Approachable introductory level?
• Important is to decide about the content to cover before we decide on style

Topics

• Pytest and/or Nose2?
  Dolf: I would prefer both, especially because people may wonder which way to go between them. We could help them decide which way they like best.
• setup.py and packaging?
  Dolf: I would say yes. I don't know CXfreeze so would be interested to read about it.
• CI?
  Dolf: One step too many IMHO. Definitely important but would take too much space I think
• Library or application?
  Dolf: I would again say both because often the two are even combined. Both very common use cases
• Native code?
  Dolf: I usually don't use native code, so have no strong opinion either way. Definitely more complex, but probably also enlightening and something many people will struggle with.
• How many packages from the project?
  Dolf: I usually keep my packages separate even if they're the same project. So different repos/packages/test/etc. A library I write on which my application for the same project depends, I still separate. I treat my library the same way I would treat any other library, so separate packaging, separate installation, etc. I list my library as a dependency/requirement in my application setup.py and make sure I install the library first (or host it online where pip can find it).
• Scripts/entrypoints?
  Dolf: I would include it as it is an often needed part in the setup.py for db setup/interaction, startup/shutdown, etc. And I am kind of messy with this at the moment so it would benefit me too if we write it down the way it shóuld be done, and then I start practising what we preach :)