Starting a Python project - poetry, pip-tools, git + GitHub, package or not?

---

In today's video I will show you how to start a Python project.

First I briefly explore poetry, but as I stopped using that tool (it does too much for me), I show my simpler + manual way of doing things these days.

I look at managing dependencies using pip-tools (pip-compile), setting up a repo on GitHub, adding a .gitignore file, working with issues and opening a pull request.

I also comment on when I use a folder structure / package or not looking at some of our repos.

I hope this is all you need to get started and I am happy to do follow up videos, just comment below ... 🙏

---
Mentioned other videos:

---
Liked our video? Be sure to subscribe for more insightful content!

[sherryab]

This is a gem of a video. I cannot begin to express how useful this is for me right now.

[RhysPowell]

Great timing on the reminder of this video in your weekly email, just at the point of having to structure a project thats grown from a single file!

[Irrazzo]

Thanks, nice video. One thing about the PR commit message "fixes long-url-of-the-issue". At least for GitHub and GitLab, you can also just write "fixes issue #1" or even "fixes #1", where #1 of course is the hashtag of that particular issue. In the browser, the hashtag will now appear as an embedded link to that issue.

[rahmansahinler]

I was just starting a side project. This video is great

[pybob]

By the way, regarding the "issue everything" (around minute 11:15), I do this more on existing + established projects, for newer projects there is first a lot of building + scaffolding going on so I am not too worried about this.

[deepknowledge]

Using poetry in azure pipeline
Autoversioning via poetry