-
Notifications
You must be signed in to change notification settings - Fork 29
Update closure-linter on pypi #97
Comments
Update: the Archlinux package (which I linked in my first post) was updated to 2.3.19 in the meantime. It now pulls the latest version directly from github. Still (even if it's not important in my workflow anymore) it would be nice to keep the pypi version up to date 😄 |
I have pushed 2.3.13 on pypi since no version was pushed at that time. I am happy to pass ownership of that package in PyPi as I don't have much time to keep the packages up to date I can update it to 2.3.19 ... but it would be one time event From this commit (339a468) it looks like the package is named gjslint it would help to get some feedback from the upstream maintainers regarding the package name as for now, there is a single tag https://github.com/google/closure-linter/tags |
I have updated a 2.3.19 wheel, but for now I am sloppy in terms of packaging on pypi... so it would still help to have someone else take care of this package on pypi |
You can have Travis CI deploy this package automatically, see: https://docs.travis-ci.com/user/deployment/pypi/ |
I have forked the repo at https://github.com/chevah/chevah-js-linter . I have refactored a few test to be more reliable and be able to run each test. Will push soon to PyPI but under a different name to not let people think that google-closure is still active. |
Here on github the last release is 2.3.19, but on pypi it's 2.3.13, and that means that linux distros will use 2.3.13. For example, ArchLinux is using 2.3.13 on the official closure-linter package.
The text was updated successfully, but these errors were encountered: