<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Hi Brian, thanks for the reply.<br>
<br>
I'm definitely excited about Pants. I see there's a pants-users
group now, but it's currently empty (as in zero posts - crickets and
tumbleweeds :) ). Would that be a good place to ask questions when I
get around to playing with Pants?<br>
<br>
It also looks like Pants development is very active right now. Would
you suggest waiting a while before diving into the docs and code? I
don't really need Pants to be super easy to use (your suggested one
year period), just to be able to understand it and maybe write a few
modules I need. I guess I'm asking if the core is stable enough for
semi-serious plugin development.<br>
<br>
Cheers!<br>
<br>
<div class="moz-cite-prefix">On 16.04.2014 19:32, Brian Wickman
wrote:<br>
</div>
<blockquote
cite="mid:CAAmsm4hK8yTYmDE7hos7h2Q4a+2TPCV1n8FHc9i5-Q0zdeJL=Q@mail.gmail.com"
type="cite">
<div dir="ltr">Pants can definitely do what you want, but you're
probably right in that it requires significant up-front
investment. It's not strictly tied to PEX files (it can
recursively generate setup.py-based projects from a transitive
closure of BUILD dependencies) but the learning curve is
non-trivial and most attention is given to the Java/Scala
backends. Python support will improve over time but it may be a
year or more before this is really easy to adopt.
<div>
<br>
</div>
<div style="">~brian</div>
<div style=""><br>
</div>
</div>
<div class="gmail_extra"><br>
<br>
<div class="gmail_quote">On Wed, Apr 16, 2014 at 12:18 PM, Tin
Tvrtković <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:tinchester@gmail.com" target="_blank">tinchester@gmail.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">Hello
packaging community,<br>
<br>
I'm investigating ways of setting up Python projects at my
workplace. We're predominantly a Java shop, but we might be
dipping our toes in Python waters (finally!) due to a
fortuitous project and my multi-year insistence, so I'm
contemplating how to set up our Python build system to
minimize workflow differences for other developers (well,
and myself).<br>
<br>
I've actually written uš a lengthy description of Maven and
why we use it but I'll spare you for now. :) To keep the
story short, I'm interested in options for setting up a
multi-module Python project. By 'multi-module' I don't mean
a single setuptools-based project with several .py files
inside, but a way of triggering a complex build process with
a single command that would build all sub-modules
(essentially sub-projects) and produce a number of end
artifacts - just like Maven. Imagine a repository containing
30 separate Django apps, packaged independently, 10 utility
libraries, 10 Django projects combining those app, and 10
RPM building projects for packaging it all up for
deployment.<br>
<br>
As far as I know, just using setuptools isn't adequate for a
workflow like this - setuptools deals with the build process
(testing, packaging, etc) of a single project only.
Solutions that come to mind are: a hierarchy of Makefiles,
shell scripts, or maybe Twitter's Pants, which sort of looks
like Maven for Python but would probably need contributions
to do what we want, and looks predisposed to building PEX
files which, while very interesting, I'm not looking to do
right now. None of these solutions are really ideal,
especially if I want to support development on Windows
(which I absolutely want).<br>
<br>
I've even thought about actually using Maven, but that's
just a Pandora's box of problems waiting to happen.<br>
<br>
I'd appreciate insight on this from anyone who's thought
about (and maybe solved) problems like this. I'm also
willing to engage and contribute to improving the situation,
especially if there's low hanging fruit to be picked. How do
other companies handle large Python repositories with a lot
of subcomponents?<br>
<br>
Kind regards,<br>
Tin<br>
_______________________________________________<br>
Distutils-SIG maillist - <a moz-do-not-send="true"
href="mailto:Distutils-SIG@python.org" target="_blank">Distutils-SIG@python.org</a><br>
<a moz-do-not-send="true"
href="https://mail.python.org/mailman/listinfo/distutils-sig"
target="_blank">https://mail.python.org/mailman/listinfo/distutils-sig</a><br>
</blockquote>
</div>
<br>
</div>
</blockquote>
<br>
</body>
</html>