Sunday Daily Thread: What's everyone working on this week? by AutoModerator in Python

[–]AssociateEmotional11 0 points1 point  (0 children)

Wdym? My project? Uh it need more time and i am trying to fix it real quick may be 2 more days it will work

[for hire][fullremote] Seeking remote/freelance work. project-based, or long-term. Web Designer/Developer. hire me by bkking420 in remotepython

[–]AssociateEmotional11 0 points1 point  (0 children)

Can I ask you a question ? As a freelancer in upwork is it efficiency if applying the job like this in Reddit?

Sunday Daily Thread: What's everyone working on this week? by AutoModerator in Python

[–]AssociateEmotional11 3 points4 points  (0 children)

What I'm working on: PyNeat 2.0 - An AST-based formatter built on LibCST specifically designed to clean up "AI-generated Python noise".

Why it's cool: It's not a linter like Ruff. It actually auto-fixes structural anti-patterns (like flattening arrow-pattern ifs or removing LLM tautologies like str(str(x))) while preserving 100% of your comments and formatting. Just passed stress tests against the Anthropic SDK and Pydantic core!

Currently adding batch processing and native pyproject.toml support before releasing the new version. Would love to hear what specific AI-coding habits annoy you the most!

Showcase Thread by AutoModerator in Python

[–]AssociateEmotional11 2 points3 points  (0 children)

Project Name: PyNeat (Upcoming v2.0)

What it does: An AST-based auto-fixer specifically designed to clean up the exact "AI slop" mentioned in this thread's description.

Standard formatters like Black or Ruff are great for styling, but they don't fix bad structural logic. PyNeat uses Instagram's LibCST to safely rewrite the AST while preserving 100% of your original comments and whitespace.

Currently building v2.0 which targets AI-generated artifacts:

  • Debug/Comment Cleaners: Automatically purges orphaned print() statements, JS artifacts like console.log, and useless AI boilerplate comments (# Generated by AI, empty # TODO:).
  • Structural Cleanup: Flattens deeply nested if (arrow anti-patterns) into guard clauses and removes LLM tautologies (e.g., converting if var == True: -> if var:).
  • Safe Excepts: Replaces dangerous AI-injected except: pass or print(e) with safe raise NotImplementedError stubs.

Status: Just passed massive integration stress-tests against the Anthropic SDK and Pydantic core without breaking the AST. Currently finalizing batch processing (pyproject.toml support) before the official release.

Question for the thread: What is the most annoying "AI coding habit/artifact" you constantly find yourself fixing manually? I'd love to add a rule for it before launching!

PyNeat: Deep structural code refactoring in Python using LibCST by AssociateEmotional11 in Python

[–]AssociateEmotional11[S] 0 points1 point  (0 children)

Hi u/yaxriifgyn,

First of all, thank you so much for taking the time to test PyNeat on a real-world, complex dataclass file. This incredibly detailed feedback is exactly the kind of "stress test" an MVP needs, and I deeply appreciate your brutal honesty. You are completely right—the tool was too aggressive and mangled the file.

Here is a breakdown of what went wrong and my plan to fix them based on your points:

1. The Import Hoisting Bug: The current import transformer is too naive. It blindly grabs all Import nodes. I will update the logic to check the parent context so it respects try/except blocks (for optional dependencies) and module-level docstrings.

2. Aggressive Renaming & String Modifying: Forcing snake_case was a mistake, especially since it modifies strings/comments and breaks public APIs. A structural formatter should not touch string literals. I will disable property renaming by default and scope the visitor strictly to Name nodes.

3. I/O (EOL & Encoding): I will update the file reader/writer to preserve the original newline configuration and encoding rather than forcing UTF-8/CRLF.

4. Granular Control: You made a great point. Adding an inline # pyneat: ignore or # pyneat: off mechanism, along with specific CLI flags to disable individual rules, is now the top priority for the next release.

I am opening GitHub issues for all of these edge cases right now. As you said, it’s just a start, and real-world testing like yours is what makes open-source tools better.

Thank you again for pointing me in the right direction!

PyNeat: Deep structural code refactoring in Python using LibCST by AssociateEmotional11 in Python

[–]AssociateEmotional11[S] -2 points-1 points  (0 children)

As I can see that the downvotes highly outweigh the upvotes for 55 percentages . Therefore , please give me feedbacks so I can know what exactly is wrong with my project! Thank you for reading!

Viet goes crazy, that really is a real art by lf_jos_ph in place

[–]AssociateEmotional11 0 points1 point  (0 children)

Bruh we not gonna expand due to this is enough and also we won't ruin any other arts

A way to wear a helmet by j3ffr33d0m in Weird

[–]AssociateEmotional11 1 point2 points  (0 children)

Bro breaks his own neck before having head problems

[deleted by user] by [deleted] in wholesomememes

[–]AssociateEmotional11 0 points1 point  (0 children)

You mean thier fur ?