r/Python • • 2d ago

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

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:

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! 🌟

5 Upvotes

2 comments sorted by

1

u/yared12qw 2d ago

Hey everyone! I've been working on an open-source VS Code and Cursor extension called V-NOC.

The idea is to make large Python codebases easier to explore. Instead of jumping between files, you can open a function or class, see its call tree, and focus on one small part of the system at a time.

Another thing I've been exploring is how we organize documentation around code.

I came across the PEP 727 discussion about attaching documentation directly to Python symbols. I found it interesting because one of the concerns was that putting documentation into annotations could make the code harder to read.

V-NOC takes a slightly different approach. You can attach Markdown documentation to functions, classes, and files without filling the source code with long descriptions. The docs are stored in the repository, tracked with Git, and organized around the code they belong to.

I'm also exploring how agents could attach plans, tasks, notes, and skills to these same nodes, so the context stays organized as the codebase grows.

I recently released the extension. It currently supports Python, with more languages planned.

I'm curious what Python developers think about this approach, especially anyone who followed the PEP 727 discussion. Would you prefer documentation organized this way, or do you think traditional docstrings are enough?

GitHub: https://github.com/yaredtsy/vnoc

VS Code: https://marketplace.visualstudio.com/items?itemName=vnoc.vnoc

PEP 727: https://peps.python.org/pep-0727/

0

u/MrAstroThomas git push -f 1d ago

Hey everyone,

I wanted also to share something: Coding on Voyager1 data (after all the light-day news).

Not really data ... but displaying the trajectory of Voyager 1 :). If you do not know how to use Coding environments, fear not. Click on the Open in Colab badge at the very top and you can execute everything directly in Google Colab (a free coding environment).

https://github.com/ThomasAlbin/Space-Science-With-Python/blob/main/2026/voyager_1_light_day.ipynb

Feel free to star my repo. After applying some graphical magic, I converted the plots in my YouTube style, like here.

Hope you like it and learn something. Let me know if you have questions.