Structuring Your Project

Re:Structuring Your Project by Datenstrom on Saturday December 07, 2019 @06:07PM (#21733226)

`poetry new`[0] is what you are looking for, previously I have used pyscaffold[1] but I like the pyproject.toml from PEP 518[2] better than all the old stuff. Unfortunately poetry does not set up docs like pyscaffold does though.

[0]: https://poetry.eustace.io/

[1]: https://pyscaffold.org/en/latest/

[2]: https://www.python.org/dev/peps/pep-0518/

[ Parent | on HN ]

Re:Structuring Your Project by ptx on Sunday December 08, 2019 @05:49AM (#21735295)

I never tried Poetry because of this somewhat worrying part of installation instructions: "The installer installs the poetry tool to Poetry's bin directory ... located at $HOME/.poetry/bin ...This directory will be in your $PATH environment variable".

The directory will be in my PATH? That makes me wonder what else it might take the liberty to reconfigure on my system.

But, reading the installer script, it seems like it at least prompts you for confirmation first, so perhaps I'll try it.

[ Parent | on HN ]

Re:Structuring Your Project by zomglings on Saturday December 07, 2019 @06:10PM (#21733244)

Nice, thank you! Will definitely check out poetry now - have been avoiding it for reasons of inertia so far. :)

[ Parent | on HN ]

Re:Structuring Your Project by theHamsta on Sunday December 08, 2019 @04:35AM (#21735084)

Psyscaffold has a --pyproject option (or at least an add-on linked in the readme, don't remember)

[ Parent | on HN ]

Re:Structuring Your Project by j88439h84 on Saturday December 07, 2019 @07:19PM (#21733582)

poetry new --src projectname

is my preference these days.

[ Parent | on HN ]