Hello Johannes,

To answer your questions:
- we don’t necessarily require a venv here; it is also perfectly possible to create the package without using the venv but I’ve recommended it anyway because it is good practice in any python project, especially for getting an overview of your dependendies.
- that information is mainly used for public repo’s, indeed. Also not really necessary for a private repo but, again, included for good practice and to demonstrate that it is possible. I’ve uploaded this package to a public repos as wel. Check out pypi here and the article here.

Thanks for your response!