megalinter
pants
| megalinter | pants | |
|---|---|---|
| 4 | 35 | |
| 710 | 3,098 | |
| - | 2.5% | |
| 9.7 | 9.8 | |
| almost 2 years ago | 5 days ago | |
| Dockerfile | Python | |
| GNU Affero General Public License v3.0 | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
megalinter
- Mega-Linter: clean all your repositories with a single action
- Mega-Linter: say good bye to ugly code on any project, for good
-
Wednesday Daily Thread: Beginner questions
Example of big class: https://github.com/nvuillam/mega-linter/blob/master/megalinter/Linter.py
pants
-
The xz attack shell script
> C/C++'s header system with conditional inclusion
Wouldn't it be more accurate to say something like "older build systems"? I don't think any of the things you listed are "modern". Which isn't a criticism of their legacy! They have been very useful for a long time, and that's to be applauded. But they have huge problems, which is a big part of why newer systems have been created.
FWIW, I have been using pants[0] (v2) for a little under a year. We chose it after also evaluating it and bazel (but not nix, for better or worse). I think it's really really great! Also painful in some ways (as is inevitably the case with any software). And of course it's nearly impossible to entirely stomp out "genrules" use cases. But it's much easier to get much closer to true hermeticity, and I'm a big fan of that.
0: https://www.pantsbuild.org/
-
Monorepo + Microservices + Dependency Managment + Build system HELL
Does pants/bazel can help me?
- Pants 2: The ergonomic build system
-
Go Dependency management in large company projects - How do you do it?
Hyper-large tech companies managing hyper-large monorepos using Bazel (google), buck (Facebook), please (thought machine), pants (Twitter, Foursquare & Square) enjoy them but also have a lot of resources devoted to running and maintaining it.
-
Reason to use other Build Tool than Make?
Yeah there's definitely some alternatives out there. Pants is another one that has a lot of traction.
-
Is it possible pickle a function with its dependencies?
You should look into pex, or it’s parent build system pants. A PEX (Python EXecutable) file can package up all your code including dependencies and run on another machine of similar OS with just an available compatible interpreter.
-
Sanity check of my decision for "Iterative AI" (DVC, MLEM, CML) pipeline over Azure ML
We don't have the CD yet, but I think what I put in place counts as simple CI (even if incomplete)? Every push & PR trigger an azure pipeline, which runs pants. This install the dependencies from the lockfile, run some linters, uses DVC to pull the data necessary for tests, and run unit tests (mypy check is deactivated until I solve a weird error). Basically the same script runs on laptops cross-platform (one of us uses Max, one Ubuntu with GPU, one Ubuntu with CPU, the scripts runs on every platform). The only difference with CI is the installation of Pants and the gestion of Cache (needs to be downloaded in CI so it takes ~3min in CI versus 20 seconds on my laptop).
- Pants 2: fast, scalable, user-friendly build system for codebases of all sizes
-
Maintain a Clean Architecture in Python with Dependency Rules
This has also been recently integrated in pants.
https://github.com/pantsbuild/pants/issues/13393
- Blazing fast CI with MicroVMs
What are some alternatives?
cicd-templates - Manage your Databricks deployments and CI with code.
Bazel - a fast, scalable, multi-language and extensible build system
cpp-linter-action - A Github Action for linting C/C++ code integrating clang-tidy and clang-format to collect feedback provided in the form of file-annotations, thread-comments, workflow step-summary, and Pull Request reviews.
megalinter - 🦙 MegaLinter analyzes 50 languages, 22 formats, 21 tooling formats, excessive copy-pastes, spelling mistakes and security issues in your repository sources with a GitHub Action, other CI tools or locally.
qodana-action - ⚙️ Scan your Go, Java, Kotlin, PHP, Python, JavaScript, TypeScript, .NET projects at GitHub with Qodana. This repository contains Qodana for Azure, GitHub, CircleCI and Gradle
please - High-performance extensible build system for reproducible multi-language builds.
SeleniumBase - 📊 Python's all-in-one framework for web crawling, scraping, testing, and reporting. Supports pytest. UC Mode provides stealth. Includes many tools.
pyflow - An installation and dependency system for Python
flake8-bugbear - A plugin for Flake8 finding likely bugs and design problems in your program. Contains warnings that don't belong in pyflakes and pycodestyle.
pyupgrade - A tool (and pre-commit hook) to automatically upgrade syntax for newer versions of the language.
beakerx - Beaker Extensions for Jupyter Notebook
Buck - A fast build system that encourages the creation of small, reusable modules over a variety of platforms and languages.