provide clj-new template to quickly start a libpython-clj project about libpython-clj HOT 2 CLOSED

Here's the thought process: In the short history of libpython-clj, the story has always been about having the best workflow in the world. If we can support more efficient project creation and more diverse workflows without increasing maintenance costs, we should!

Using the lein-tools-deps plugin in project.clj means we only need to update the :deps in deps.edn but lein commands will work exactly the same as before. That way we get combined advantages of Leiningen and tools-deps for developing against libpython-clj.

Additionally, we can encourage adoption of libpython-clj by providing a simple quickstart with clj-new. As we increment the versions, we can update the clj-new template for libpython-clj, ensuring that users are always getting the best experience. We can also optionally extend the template over time, adding examples, tutorials, Dockerfiles, and different system configurations options with the +opt notation, i.e., clj -A:new libpython-clj mydomain.myapp +python3.7 +lein +tutorial +virtualenv or +conda or +linux or +mac or +windows etc.

Extending this would also be a great way for other developers to get involved.

from libpython-clj.

When we publish to clojars with the format libpython-clj/clj-template, that's how we get access to the syntax clj -A:new libpython-clj .... See examples

from libpython-clj.