Hi Alessandro,

On Wed, Apr 11, 2018, 11:41 Alessandro Molina <alessandro.mol...@gmail.com>

> On Tue, Apr 10, 2018 at 10:04 PM, Thomas De Schampheleire <
> patrickdeping...@gmail.com> wrote:
>> There is also an open point about the 'watch' feature and whether or
>> not it should be integrated in gearbox --reload rather than
>> introducing a new 'nodemon' mechanism.
>> The introduction of 'npm run X' has also raised some comments in the
>> past regarding cross-platform support. These is IMHO not bikeshedding,
>> it's about being careful in adding extra complexity or going in a
>> wrong direction.
> Hi Thomas,
> If node is just involved in compiling js/css and bundling assets you might
> want to have a look at
> https://github.com/amol-/dukpy
> It's a project that I created exactly to avoid the need to have two
> dependency managers (npm and pip)
> and two execution environments (python and node) for a Python web app.
> It has a builtin less compiler (
> https://github.com/amol-/dukpy#less-transpiling ) which is integrated
> with WebAssets ( https://webassets.readthedocs.io/en/latest/ ) to
> generate css bundles out of less files without the need to install
> node/lessc.
> And through support for npmjs.org (
> https://github.com/amol-/dukpy#installing-packages-from-npmjsorg ) it's
> in theory possible to have setup.py also install node dependencies.

Thanks a lot for this information.
If I understood correctly you wouldn't even need npm at all, correct?

Do you know of an example project that is using this?
Where would you handle this bundle creation and nodejs downloads? From
setup.py? From a gearbox command?

And do you have suggestions with respect to the handling of external
asserts when creating a pypi package, in particular taking into account
licensing aspects of the GPL (Kallithea is a gplv3 project).

kallithea-general mailing list

Reply via email to