-
-
Notifications
You must be signed in to change notification settings - Fork 108
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Dependency Management #9
Comments
Hi and thank you! Thx for reaching out. Right now I'm just using entries in the
Which takes care of collecting everything automatically. It looks like the |
yeah, you only need to specify them explicitly in the The file |
I see, thanks for the suggestion. I need to learn more about |
@paketb0te I'm playing around with poetry and got a similar Just a few questions about some extra info that is currently in the -url Do you know how these can be specified with poetry? |
According to the docs, we can just specify those in So it would look something like this: [tool.poetry]
name = "git-sim"
version = "0.1.2"
description = "Simulate Git commands ..."
authors = ["Jacob Stopak <jacob@initialcommit.io>"]
license = "MIT"
readme = "README.md"
packages = [{include = "git_sim"}]
homepage = "https://git-sim.org/"
keywords = ["git", "sim", "simulation", "..."]
repository = "https://github.com/initialcommit-com/git-sim
... If I understand correctly, you can define the equivalent to edit: Apparently you can also define arbitrary URLs besides homepage and repo: urls |
In relation to #85 I'm not well experienced packaging big projects but small ones.
Again about 2. and 3. This are not bad tools. The problem is just that they are recommended in every blog post etc. But they are intended to solve problems that "small projects" usually don't have. Keep your solutions grounded. If you like you can contact me and I explain you my real world projects how I solved somethings just using pyproject.toml not using anything else. |
Hi @buhtz, thanks for your input on this. I was not aware that you can also specify dependencies in -> That kinda obsoletes the usage of poetry for now, I guess. @initialcommit-io let's close this issue. |
Sounds good @paketb0te, closing this one for now so |
Once again, this is a great tool!
Can I interest you in using
poetry
for packaging and dependency management?I had pretty good experiences with it, can definitely recommend.
If you prefer a simpler approach like
requirements.txt
that's fine too (but I really recommend to take a look at poetry 😆)(Would look something like THAT)
The text was updated successfully, but these errors were encountered: