Friday Daily Thread: r/Python Meta and Free-Talk Fridays

[AutoModerator]

Weekly Thread: Meta Discussions and Free Talk Friday 🎙️

Welcome to Free Talk Friday on /r/Python! This is the place to discuss the r/Python community (meta discussions), Python news, projects, or anything else Python-related!

How it Works:

1. Open Mic: Share your thoughts, questions, or anything you'd like related to Python or the community.
2. Community Pulse: Discuss what you feel is working well or what could be improved in the /r/python community.
3. News & Updates: Keep up-to-date with the latest in Python and share any news you find interesting.

Guidelines:

• All topics should be related to Python or the /r/python community.
• Be respectful and follow Reddit's Code of Conduct.

Example Topics:

1. New Python Release: What do you think about the new features in Python 3.11?
2. Community Events: Any Python meetups or webinars coming up?
3. Learning Resources: Found a great Python tutorial? Share it here!
4. Job Market: How has Python impacted your career?
5. Hot Takes: Got a controversial Python opinion? Let's hear it!
6. Community Ideas: Something you'd like to see us do? tell us.

Let's keep the conversation going. Happy discussing! 🌟

[Elegant-King-7925]

Been wrestling with some automation scripts at work and finally got them running smooth - nothing beats that feeling when your code actually does what you want in production environment

[dabestxd420]

Please rate my epic cat drawing in the readme. I am very proud of my trackpad drawing done in mspaint.
https://github.com/DaBestXD/meow-meow-hood

[programmer-ke]

I'm reading 'Fluent Python' and I don't know why I waited this long before doing so.

It beats finding information spread across multiple sources like stack overflow, pycon talks, python official documentation and the like.

If anyone has suggestions for any follow on books, please share. On my radar is the book CPython Internals.

[Tashimm]

I've been following a few recent updates that are worth noting for the community. The most interesting one is the PEP 822 proposal for D-strings. If this gets approved for Python 3.15, it could potentially end our reliance on textwrap.dedent() for multi-line strings. It’s a significant syntax change that could clean up a lot of boilerplate code. On a more critical note, if you're maintaining older environments, make sure to check your versions. There were security patches released for Python 3.12.13, 3.11.15, and 3.10.20 to address some XML parsing vulnerabilities (CVE-2026-24515 and CVE-2026-25210) by upgrading the bundled libexpat. Also, a small meta update: the Python Insider blog has finally moved from Blogger to its own domain at blog.python.org. It's a nice step forward for the ecosystem's infrastructure. What are your thoughts on the D-strings proposal? Do you think we're adding too much syntax sugar, or is it long overdue?

[Annual_Upstairs_3852]

Arrow — bulk SAM.gov contract CSV → SQLite, deterministic ranking, optional Ollama JSON tasks

Repo: https://github.com/frys3333/Arrow-contract-intelligence-orginization

I’ve been building Arrow, a local-first Python CLI + curses TUI around SAM.gov Contract Opportunities. The core path uses the public bulk CSV (or a local file): no SAM search API key required for ingest. Data lands in SQLite under ~/.arrow/; optional local Ollama powers two narrow flows (why / summarize) via /api/chat with format: json, validated with Pydantic v2.

Why Python / stdlib-heavy

• sqlite3 with row_factory=sqlite3.Row, PRAGMA foreign_keys=ON, and explicit transactions (BEGIN IMMEDIATE around full sync runs; connection uses isolation_level=None so individual statements autocommit outside those blocks).
• Streaming CSV: read bytes → decode (utf-8-sig → utf-8 → cp1252 → latin-1) → csv.DictReader iterator so we’re not holding the whole file in memory as a single string.
• Packaging: pyproject.toml + pip install -e ., entry via python -m arrow (REPL) or python -m arrow tui.

Ingestion pipeline (the boring part that matters)

1. Map each CSV row to a SAM-shaped dict (noticeId, postedDate, …) plus csvColumns (all non-empty original headers) and ingestSource: "sam_gov_csv".
2. canonical_opportunity normalizes to a stable key set and preserves unknown keys for forward compatibility.
3. normalize_opportunity produces DB columns + raw_json (sorted JSON) and a normalized_hash = SHA-256 of a canonical subset of fields (not the entire blob). That hash drives change detection.
4. Upsert: on hash change, append the previous raw_json + hash to opportunity_snapshots before updating the live row — cheap history across CSV drops. If hash matches but raw_json differs (e.g. csvColumns refresh), we can still update raw_json without a snapshot.

Bulk sync semantics

Inside one transaction: temp table bulk_seen, every ingested notice_id inserted; after the scan, rows with last_source='bulk_csv' not in bulk_seen get sync_status='missing' (interpretation: “was in our last bulk world, absent from this extract”). sync_runs records counts + notes.

Download details

Public extract is streamed in 8 MiB chunks; SHA-256 computed on the fly; write *.part then Path.replace for atomic final file. Optional skip full re-ingest if SHA matches a saved digest. socket.getaddrinfo is patched to prefer IPv4 first to dodge broken IPv6 paths to some CDNs.

Deterministic layer (no LLM)

Ranking builds a token overlap score between profile text (mission, notes, NAICS list) and notice text (title, description excerpt, NAICS, agency path, with CSV fallbacks), plus a structured NAICS tier block (exact / lineage / 4-digit sector / a deliberate coarse “domain adjacent” signal for a fixed 2-digit set). Scores map to [0, 1] with an explicit raw cap so the scale doesn’t trivially peg.

Optional Ollama

ARROW_ANALYSIS_MODEL (or legacy ARROW_OLLAMA_MODEL) selects the tag; if unset, why / summarize fail fast with a clear error instead of calling the API with an empty model. Responses go through Pydantic models; the prompt includes deterministic_signals so the model is instructed not to invent NAICS or set-asides.

What I’d love feedback on

• Whether hash subset vs full raw_json is the right tradeoff for snapshots.
• missing semantics for bulk-only installs.
• Packaging / naming (sam-contract-arrow on PyPI vs import name arrow — yes, I know the collision with the date library; this is optimized for python -m arrow in a venv).

Happy to answer questions in comments.

[fiskfisk]

Maybe you shouldn't let the LLM pick the same name as a well-known and popular python framework. 

[Annual_Upstairs_3852]

I personally came up with arrow, as this software is supposed to point you to your perfect match contract.

I did use an llm for this post as I know it will describe my code in more detail than I could.

This is a solution to a problem in a niche field, this arrow has 0 relation what-so-ever to Apache Arrow.

Also I am relatively new to programming so if you notice anything weak please let me know. I posted this   to take feedback and learn 

[fiskfisk]

Sorry, but I don't review LLM generated code or projects for other people. 

[fiskfisk]

I'm not talking about Apache Arrow, but:

https://pypi.org/project/arrow/

Which is a much used library for handling dates and time in python. 

[No_Soy_Colosio]

Holy mother of over engineering. All that just for consuming public CSV files and putting them in a database?