Thema

#python

Loots, Blogposts und verwandte Themen rund um diesen Tag. Folge dem Tag, damit passende Updates in deinem Orbit bleiben.

#python
7Gezeigte Loots
2Gezeigte Artikel
8Verlinkte Nachbar-Tags
Anschluss-Themen

Wenn du tiefer einsteigen willst, helfen die benachbarten Tags beim Vergleichen und Querlesen.

Loot

Mehr aus diesem Thema

Alle Loots entdecken

Scrape Changing Websites with Anansi Self-Healing Selectors and MCP

No votes yet
A Python crawler for unstable or JavaScript-heavy sites, with selector healing, structured-data extraction, adaptive rate limiting, and an MCP server for agent-driven crawling. Use only for authorized scraping. Anansi is a Python web scraping toolkit designed for sites that change often or need browser rendering. It combines adaptive parsing, structured-data extraction, incremental crawling, proxy support, and an MCP server so an LLM or agent workflow can drive fetch, extract, crawl, pause, resume, export, and metrics actions. Why it is useful Self-healing selectors: stores selector confidence and attempts fallback strategies when a layout changes. Structured extraction first: pulls JSON-LD, Open Graph, and Microdata before relying on brittle CSS selectors. Browser upgrade path: can switch from HTTP fetching to Playwright rendering for JavaScript-heavy pages. Crawler durability: includes an async crawler, SQLite-backed queue, incremental recrawls, ETag/Last-Modified handling, and resumable jobs. Agent-ready interface: ships with an MCP server so compatible LLM tools can operate crawls through tool calls. Best fit Use Anansi when you need a resilient research or data-extraction crawler for websites you are allowed to access, especially where pages change structure or require JavaScript rendering. It is most relevant for developers building data pipelines, monitoring workflows, competitive research dashboards, or agentic browsing systems. Quick evaluation checklist Confirm the target website permits your intended crawling use case. Start with structured data extraction before custom selectors. Enable browser rendering only where HTTP fetching is insufficient. Keep adaptive rate limiting active and respect Retry-After responses. Use the MCP server when you want an agent to orchestrate crawl tasks instead of manually scripting every step. Source notes The GitHub repository describes Anansi as a self-healing web scraper with selector repair, browser rendering fallback, Chrome-like TLS fingerprinting, Pydantic validation, incremental crawling, and an MCP server. The project is written primarily in Python and is licensed under Apache-2.0.
LinkLoot access
Free
Provider costs
Unknown
Review open
0

Automate Job Applications Using Your Daily Driver Browser

No votes yet
Text: AI-generated
AI-generated · Automatically published by LinkLoot. SHOBR automates the tedious parts of job hunting—scraping, resume tailoring, and application prep—by driving your actual authenticated browser. No headless bots, no credential extraction. AI-generated: This Loot was created and published automatically by LinkLoot and was not substantively reviewed by a human editor. What it does SHOBR (Simulate Human Occupational-Bureaucratic Rituals) is a UNIX-style job search automation tool that prepares applications while keeping you in control. It uses beachpatrol to drive your existing daily-driver browser for scraping jobs with your real authenticated sessions, then leverages minimal LLM calls to tailor resumes from Markdown into ATS-readable PDFs via Groff and Pandoc. The workflow follows a human-in-the-loop model: SHOBR discovers jobs, screens them, writes drafts, and builds deliverables—but never auto-submits. You approve each application step manually. All data lives in append-only JSONL event logs, so you can interrupt pipelines or recompute decisions with new rules anytime. Who it helps Job seekers who want to automate repetitive tasks (finding listings, tailoring CVs) without resorting to "spray and pray" mass applications or risky headless browsers that trigger detection. Particularly useful for those targeting platforms like LinkedIn where authenticated access matters and bot detection is aggressive. Developers comfortable with Python and CLI tools will appreciate the modular design. The project avoids demanding an agent framework—it's lean enough (3500 LOC) to extend yourself if needed. Getting started Prerequisites: Install beachpatrol first (the hard dependency). See its README for setup. Python 3.14+ Installation: The toolchain requires Groff and Pandoc for PDF compilation. Ensure these are available on your system. LLM configuration: SHOBR uses any-llm abstraction, supporting OpenAI, Anthropic, local models, or even hijacking subscriptions via faaah. Configure your preferred provider before running. Limits and costs No auto-submit: Final application clicks remain manual by design. LLM costs: Resume tuning needs some LLM usage; budget for API calls if using cloud providers. Browser dependency: Requires beachpatrol, which itself needs proper setup as your daily driver. MIT licensed: Free to use, modify, distribute. Hosting/execution costs depend on your infrastructure choices. Early-stage tool: Built with stdlib unittest, full E2E TDD, but expect rough edges typical of personal projects. Source links Official repository Project documentation License
LinkLoot access
Free
Provider costs
Unknown
Review open
0

Background jobs and cron for Python without Redis or RabbitMQ

No votes yet
Text: AI-generated
AI-generated · Automatically published by LinkLoot. Run scheduled tasks and background workers in Django apps, scrapers, and CLIs using only SQLite—no broker, no daemon, zero dependencies. AI-generated: This Loot was created and published automatically by LinkLoot and was not substantively reviewed by a human editor. What it does tinyjobs brings Celery-style task queuing to Python projects that don't need the infrastructure overhead. Instead of requiring a Redis or RabbitMQ instance before running a single job, it uses a plain SQLite file as its queue. You define tasks with decorators supporting retries, timeouts, and async execution, then enqueue them from anywhere—including synchronous code. The library handles the lifecycle: queued → running → success or failure. When you need current status, call job.refresh() explicitly; attribute access never triggers I/O silently. Results are off by default since most jobs run for side effects, avoiding write amplification on hot paths. Terminal jobs get pruned automatically. Successes stay for a week, failures for thirty days (because those are what you debug). Multiple workers coordinate pruning through a single conditional UPDATE on a marker row—forty workers still means one sweep per interval, no leader election needed. Who it helps This targets developers building Django email senders, nightly scrapers, or CLI tools that offload slow work. If your project never needed distributed task queues but wants reliable scheduling, tinyjobs fits. The documentation notes that when you outgrow SQLite, switching the URL to Redis leaves your task code unchanged. Getting started Install via pip, then initialize with a SQLite path: Define tasks with decorators like @app.task(maxattempts=5, timeout=300). Enqueue returns a snapshot of the database row—not a live handle—so the worker process updates state independently. Use job.wait(timeout=30) to block until completion, or await job.awaited(timeout=30) from async contexts. CLI commands manage retention policies directly: tinyjobs worker --retain-failed 90d or tinyjobs purge --before 30d --dry-run. Limits and costs Pruning doesn't shrink the SQLite file; freed pages get reused internally, so databases plateau rather than contract. Reclaiming filesystem space requires manual VACUUM, which demands exclusive access. MIT-licensed open source. No pricing information provided in the packet. Source links Official repository Project documentation License
LinkLoot access
Free
Provider costs
Unknown
Review open
0

Deterministic memory for AI agents that tracks current facts and reports freshness

No votes yet
Text: AI-generated
AI-generated · Automatically published by LinkLoot. TenseMem gives AI agents a single SQLite-backed memory layer that keeps one current truth per slot, tells you whether a read is fresh, and refuses to learn from its own output. AI-generated: This Loot was created and published automatically by LinkLoot and was not substantively reviewed by a human editor. What it does TenseMem provides embedded, deterministic state memory for AI agents. The model proposes typed operations (add, set, correct); a rule engine decides what is actually stored. One SQLite file inside your process holds the data—no server required. Each fact lives in a named slot. A new value supersedes the old one, but history still answers “where did I live before?” Every read reports asofseq, pending, and iscurrent, so callers know whether an extraction has finished applying. Recalled context is fenced, and the extractor needs a verbatim user quote to learn, preventing self-echo contamination. Who it helps Developers building agent systems where stale or contradictory memory causes real errors. If similarity search returns both “I live in Delhi” and “I moved to Bangalore” and leaves the LLM guessing, TenseMem’s slot model gives you one authoritative answer plus an audit trail. It suits Python services, CLI tools, REST APIs, or MCP integrations that need lightweight persistence without running separate infrastructure. Getting started Install via pip with optional provider extras: tensemem[openai], tensemem[anthropic], tensemem[ollama], tensemem[litellm], or Gemini (GEMINIAPIKEY in environment). The default FakeExtractor is rule-based and needs no API key, useful for local testing. The repository includes a packaged benchmark (tensemem bench) that scores 101 conversations offline with FakeExtractor. Architecture docs map every surface—Python, CLI, REST, MCP—to source files, and the test suite locks core invariants against auto-registering unknown predicates or teaching from fenced text. Limits and costs Apache-2.0 licensed open source; hosting costs depend on your deployment. Provider keys go in process environment only. The default store is a single SQLite file with one writer thread, which may limit concurrent writes in high-throughput setups. Freshness guarantees apply within a single process; distributed deployments need external coordination not described here. Source links Official repository Project documentation Project license
LinkLoot access
Free
Provider costs
Unknown
Review open
0

Run Low-Cost, Deterministic Computer Use with TypeSafe

No votes yet
Text: AI-generated
AI-generated · Automatically published by LinkLoot. A beta Python toolkit that drives macOS (and experimentally Windows) from plain-English goals by combining deterministic screen reading with a small classifier. AI-generated: This Loot was created and published automatically by LinkLoot and was not substantively reviewed by a human editor. What it is typesafe-computer-use is an open-source computer-use loop for Python 3.12+. It reads the screen, chooses from a bounded set of actions with a TypeSafe decision model, and reserves a writing model for text entry or final screen interpretation. Where it fits Use it for controlled browser or desktop automation when a task can be expressed as a sequence of clicks, navigation, and occasional text entry. The repository documents a clicker command, a dry-run mode, configurable model endpoints, and a cost/latency comparison against screenshot-heavy frontier-model loops. Setup and limits The documented setup uses uv, a TypeSafe API key, and optionally an Anthropic-compatible or OpenAI-compatible writer/answer endpoint. macOS 14+ is the primary platform; Windows 10/11 support is marked experimental. The project is explicitly beta software and can drive a real mouse and keyboard, so start with dry runs and an isolated browser profile. Do not treat the repository’s benchmark figures as an independent performance guarantee. The code is MIT-licensed. Review the current repository, dependencies, permissions, and endpoint configuration before using it on a machine with sensitive accounts or data.
LinkLoot access
Free
Provider costs
Unknown
Review open
0

Run Rust-backed Python data pipelines with Rivers

No votes yet
Text: AI-generated
AI-generated · Automatically published by LinkLoot. Rivers is a new open-source orchestration platform for data and ML pipelines: Python definitions, Rust control plane, Kubernetes operator, OIDC, and forward-auth support. AI-generated: This Loot was created and published automatically by LinkLoot and was not substantively reviewed by a human editor. Rivers is worth a bookmark if you build data or ML pipelines and want a Python authoring layer without putting the whole control plane on Python runtime behavior. The project defines assets and repositories in Python, then uses a Rust core for graph resolution, execution planning, scheduling, partition handling, and the web UI. What to try Define simple assets as Python functions and materialize them locally with pip install rivers. Use rivers dev MODULEPATH for a single-process local setup with embedded storage, scheduler, and UI. Evaluate it against Dagster-style asset orchestration needs where startup speed, typed execution planning, and Kubernetes deployment matter. Check the Kubernetes path if you need CodeLocation CRDs, one-pod-per-step execution, Helm charts, and a separate operator. Review the authentication guide before exposing the UI: Rivers documents none, native OIDC with PKCE, and forward-auth mode behind a trusted proxy. Good fit Rivers looks most useful for teams experimenting with data asset orchestration, ML pipeline scheduling, or internal pipeline platforms that want Python ergonomics plus a compiled Rust scheduler/control plane. It also has practical production hooks: SurrealDB-backed state, Server-Sent Events for UI updates, Kubernetes-native execution, backfills, sensors, schedules, concurrency limits, and pluggable IO. Caveats This is still a young project. The GitHub repository was created in May 2026 and the PyPI package is at 0.4.0, so treat it as an evaluation candidate rather than a drop-in replacement for mature orchestrators. The repository license is AGPL-3.0, which matters for internal platform and SaaS use. LinkLoot has not performed a hands-on review; verify installation, security posture, and operational behavior in a disposable environment before using it with production workloads.
LinkLoot access
Free
Provider costs
Unknown
Review open
0

Build self-evolving agent workflows with EvoAgentX

No votes yet
An open-source Python framework for generating, evaluating, and improving multi-agent workflows from goals and feedback. What it is EvoAgentX is an open-source framework for building LLM-based agents and agent workflows that can be generated, evaluated, and improved over time. Instead of manually wiring every prompt chain, you describe a goal, generate a workflow, attach agents, and execute the result through the framework. Who it helps Use it if you are experimenting with multi-agent systems, benchmark-driven agent improvement, or human-in-the-loop workflow design. The project is especially relevant for researchers, automation builders, and teams that want to compare agent behavior across models rather than only ship a single prompt. How to evaluate it Start with a small non-production workflow and inspect the generated graph before execution. Check the built-in evaluation layer, memory module, and toolkits for filesystem, browser, search, databases, and code execution. The repository documents pip install evoagentx and source installation options, but real workflows will require model credentials such as an OpenAI-compatible API key. Limits and risks EvoAgentX can connect agents to tools that touch files, browsers, APIs, and code execution. Keep early tests inside a sandbox, use throwaway keys, and review generated workflows before allowing external effects. Treat self-evolution as an optimization loop, not proof that the workflow is safe or correct. Sources Primary source: https://github.com/EvoAgentX/EvoAgentX Documentation and examples are linked from the repository README.
LinkLoot access
Free
Provider costs
Unknown
Review open
0
Blog

Verwandte Artikel

Blog durchsuchen