On 09/29/2017 03:34 AM, Jimmy Thrasibule wrote:
> Now come the hard part. Our team is too small to get the project
> divided in multiple sub-projects and I would also like to keep
> distribution as simple as possible meaning keeping only one
> ``setup.py`` so that with one ``./setup.py bdist``, I can create
> **all** the packages I need to distribute the project.
>
> And indeed I'd like to have multiple packages for this one project so
> I can install only the required dependencies for each subsystem. In
> the end, I'd like to get a distribution package for the following:
>
> * myproj.common
> * myproj.data
> * myproj.server
> * myproj.tasks.common
> * myproj.tasks.task1
> * myproj.tasks.task2
>
> Any idea how I can get this far keeping the overall project management
> as simple as possible?
The simplest solution: assuming this is a purely "bespoke" project (only
your team runs the app), I would just ditch the "install only required
dependencies" bit: the size of the software load should be minimal on a
modern system, and keeping the hosts / VMS interchangeable makes for a more
flexible deployment.
If you really cannot do that, then 'setup.py' can contain multiple
invocations of the 'setuptools.setup()' function, once for each separate
sdist / wheel you want to build ('bdist' support is already deprecated in
modern setuptools, and pip has never been able to install those artifacts).
Tres.
--
===================================================================
Tres Seaver +1 540-429-0999 [email protected]
Palladion Software "Excellence by Design" http://palladion.com
--
You received this message because you are subscribed to the Google Groups
"pylons-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/pylons-discuss/oqll1b%24uo1%241%40blaine.gmane.org.
For more options, visit https://groups.google.com/d/optout.
