Quoting Sébastien Delafond (2019-01-31 12:25:05) > On Jan/31, Jonas Smedegaard wrote: > > The underlying issue is that the "js" in python-jsbeautifier stands > > for JavaScript, and python-jsbeautifier fail to properly expose the > > JavaScript part of the project as a shared library! > > > > The straightforward solution is for python-jsbeautifier to also build > > libjs-beautify and node-beautify! > > I unfortunately do not have the available bandwidth to work on that, and > I'm not also not particularly interested in maintaining any node-* > stuff. > > I'm however totally fine with someone taking over python-jsbeautifier > and doing just that.
Fair enough. I have no problem handling the Python parts of this project. We can have the source package node-js-beautify provide the Python parts, then! @Sébastien: You are of course more than welcome to help out in any way you want with the (upcoming) Python part of that node-js-beautify! I suggest this way forward: 1) Release node-js-beautify to unstable with no executable at all 2) Release node-js-beautify to experimental adding python package 3) Release node-js-beautify to unstable when 1) is in testing I am quite busy elsewhere today, so if others can handle 1) it would be great! - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private
signature.asc
Description: signature