Add a basic example for python/behave

[alef75]

🤔 What's changed?

just add a basic example of python behave in a eclipse pydev project

⚡️ What's your motivation?

🏷️ What kind of change is this?

• 📖 Documentation (improvements without changing code)
• 🏦 Refactoring/debt/DX (improvement to code design, tooling, etc. without changing behaviour)
• 🐛 Bug fix (non-breaking change which fixes a defect)
• ⚡ New feature (non-breaking change which adds new behaviour)
• 💥 Breaking change (incompatible changes to the API)

♻️ Anything particular you want feedback on?

📋 Checklist:

• I agree to respect and uphold the Cucumber Community Code of Conduct
• I've changed the behaviour of the code
  • I have added/updated tests to cover my changes.
• My change requires a change to the documentation.
  • I have updated the documentation accordingly.
• Users should know about my change
  • I have added an entry to the "Unreleased" section of the CHANGELOG, linking to this pull request.

---

This text was originally generated from a template, then edited by hand. You can modify the template here.

[jenisys]

Some minor issues

[jenisys]

BETTER USE: default_format instead of format

default_format = pretty

REASON:

• format appends to a list of formatters from config-file and command-line (you cannot easily override it)
• If you use behave -f plain … you override the formatter but still get an pretty.output file because you specified no outfiles = ….
• ALTERNATIVE: pretty is already the default formatter if you do not specify one. Therefore, you can remove it from the config-file w/ the same effect.

[jenisys]

BETTER USE: The newest stable behave version which is currently 1.3.3.

behave >= 1.3.3

[laeubi]

@jenisys if you review the code you can mark a line and then there is a litte icon "suggest change" when you use this:

1. it shows a nice diff of what you propose to change
2. one can use that to directly commit/accept your suggestion