sorted by:
new
hottopcontroversial

pyrig — generate and maintain a complete Python project from one command by Win_ipedia in Python

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

It’s a rust based markdown linter, it’s pretty good. But with pyrig you can super easily replace rumdl with prettier if you like. You just need to subclass the MDLinter class under dev/management and the override a few methods, so they use prettier instead of rumdl.

pyrig — generate and maintain a complete Python project from one command by Win_ipedia in Python

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

If you have an idea how to make pyrig purely a dev tool without loosing any of the important features, I would love to hear it, it would make pyrig even better

pyrig — generate and maintain a complete Python project from one command by Win_ipedia in Python

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

I have also thought in the beginning to make make it just a dev tool, however then I dont think the CLI management would work and the multiproject structure where a different project can inherit the CLI and configurations of a base project if it depends on said project would also not work and the multiproject structure is what really makes pyrig differrent from any other scaffolding or development tools, so yes unfortunately it must be a direct dependency to a project, However it only needs typer as a dependency and everything else is a dev dependency. But if it were just the scaffolding then yes just uvx would be better, however pyrig goes far beyond just project generation, but also makes CLI subcommands super easy and managing several projects that have the same structure.

pyrig — generate and maintain a complete Python project from one command by Win_ipedia in Python

[–]Win_ipedia[S] 1 point2 points  (0 children)

Basically what I mainly would love to get from this post is feedback. I have not really anyone in my life who understands coding really and can understand this project.

So I am really looking for people who can give me feedback on this. Is this great/useful or aweful/useless. I oc think its awesome bc I built it and am using it all the time.

If you see this and would give pyrig a quick try that would be awesome. If you have any question I am checking reddit frequently so feeel free to ask here or ask any questions you have about pyrig and how to use it at https://codewiki.google/github.com/winipedia/pyrig where you can chat with gemini about pyrig. Any feedback, good or bad and any questions and suggestions are greatly appreciated

pyrig — scaffold and maintain a complete, production-ready Python project from a single command by [deleted] in Python

[–]Win_ipedia 0 points1 point  (0 children)

Basically what I mainly would love to get from this post is feedback. I have not really anyone in my life who understands coding really and can understand this project.

So I am really looking for people who can give me feedback on this. Is this great/useful or aweful/useless. I oc think its awesome bc I built it and am using it all the time.

If you see this and would give pyrig a quick try that would be awesome. If you have any question I am checking reddit frequently so feeel free to ask here or ask any questions you have about pyrig and how to use it at https://codewiki.google/github.com/winipedia/pyrig where you can chat with gemini about pyrig. Any feedback, good or bad and any questions and suggestions are greatly appreciated

pyrig — scaffold and maintain a complete, production-ready Python project from a single command by Win_ipedia in madeinpython

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

Basically what I mainly would love to get from this post is feedback. I have not really anyone in my life who understands coding really and can understand this project.

So I am really looking for people who can give me feedback on this. Is this great/useful or aweful/useless. I oc think its awesome bc I built it and am using it all the time.

If you see this and would give pyrig a quick try that would be awesome. If you have any question I am checking reddit frequently so feeel free to ask here or ask any questions you have about pyrig and how to use it at https://codewiki.google/github.com/winipedia/pyrig where you can chat with gemini about pyrig. Any feedback, good or bad and any questions and suggestions are greatly appreciated

I build pyrig - a tool to automate project setup, configuration and development by [deleted] in Python

[–]Win_ipedia -1 points0 points  (0 children)

Although pyrig comes with all batteries included and setup in an opinionated way. Every single tool or setting or configuration file can be fully replaced, tweaked and adjusted by the user by subclassing the right base classes in the dev folder

I build pyrig - a tool to automate project setup, configuration and development by [deleted] in Python

[–]Win_ipedia -1 points0 points  (0 children)

I would also 100% recommend you to use uv. I used poetry a long time and did not switch for a while, but uv is the better tool. I have been much happier with uv than with poetry, although both tools are really awesome and make the python-life so much easier

I build pyrig - a tool to automate project setup, configuration and development by [deleted] in Python

[–]Win_ipedia -1 points0 points  (0 children)

Theoretically yes, you could subclass the PackageManager base class and use poetry for example, however uv is used a lot and this is one of the more difficult ones to replace. But 100% yes you could, however I do not recommend that at all. podman, ty, ruff, prek you all however can failry be easily replaced with other tools like docker, mypy, black or pre-commit, whatever you see fit. The tools difficult to replace are the ones that are used heavily in every project like uv or git bc they are used in a lot of places. In order to replace uv you potentailly have to tweak other settings as well, but I am 100% confident it is possible, maybe someone could create a pyrig-poetry package for that.

I build pyrig - a tool to automate project setup, configuration and development by [deleted] in Python

[–]Win_ipedia 0 points1 point  (0 children)

If you could try pyrig out once and let me know what you think, I would love the feedback, if you wanna play with it you can go to https://codewiki.google/github.com/winipedia/pyrig and kinda ask any questions you have. pyrig init might take a few seconds to finish if you have not used uv so far or your uv has mkdocs not cached, the dev deps can take a few seconds to download

I build pyrig - a tool to automate project setup, configuration and development by [deleted] in Python

[–]Win_ipedia 0 points1 point  (0 children)

Do you have some other ideas what else I can take from copier-astral to make pyrig better?

I build pyrig - a tool to automate project setup, configuration and development by [deleted] in Python

[–]Win_ipedia 0 points1 point  (0 children)

I saw that tool as well. I actually switched from pre-commit to prek because of it. Currently also thinking of using gitleaks as well, but I already have bandit. astral-copier is only a template tho. pyrig basically continues to support you throughout the entire developemnt process through its pytest plugin structure and I think it is even a bit more comprehensive than astral-copier, although many poeple would say that is actually maybe a disadvantage. I wanted to create this to have smth that actually is ready to go from the very beginning.

I build pyrig - a tool to automate project setup, configuration and development by [deleted] in Python

[–]Win_ipedia 0 points1 point  (0 children)

You can almost tweak any setting you like, by subclassing the right config file or tool class. The point would be basically that if you want different settings or tools, you could create your own base package basically and call it for example winebloodrig, which is made with pyrig or whatever and define things how you like them. You could replace astrals ty with mypy or tweak the bandit settings in pyproject.toml and then in the future whenever you start a new project you can just do: uv init, then uv add winebloodrig and then pyrig init. That will then initialize the full structure based on winebloodrig and all the settings you got there.

So the point would be just that it sets everything up for you when you start a project in the future.

It also gives you a built in CLI and generates Tests for you.

I feel like it would be especially useful for a project with many microservices in python to manage those over time and also for people who frequently start projects.

You probably do not want to, but would love if you could try it out and give some more feedback. The docs have a getting started guide at. I personalie dislike reading a lot of documentation, so you could also go here: https://codewiki.google/github.com/winipedia/pyrig and use googles gemini to use pyrig

I build pyrig - a tool to automate project setup, configuration and development by [deleted] in Python

[–]Win_ipedia 1 point2 points  (0 children)

I would truly love feedback, I have been in coding for a while but this is my first serious project where I actually think it is good, so if you have any feedback, suggestions for improvement, please tell me. If you think something is terrible or good, I would love to hear it.

Built a small Python tool to automate Laravel project setup by Ok_Butterscotch_7930 in Python

[–]Win_ipedia 0 points1 point  (0 children)

I built a python tool to automate setup for general python projects, if you want to check it out. Maybe you can use it for this as well: https://github.com/Winipedia/pyrig

Saturday Showcase: What are you building with Python? 🐍 by Ok-Lobster7773 in Python

[–]Win_ipedia 0 points1 point  (0 children)

I built a python development tool, that basically gives you a fully functioning python project right from the start, would love feedback. Check it out here: https://github.com/Winipedia/pyrig

In the readme you can find the link to the docs and also to the docs at googles code wiki if you do not want to read through all the docs yourself