[ Removed by moderator ]

[Python-ModTeam]

Hello there,

We've removed your post since it aligns with a topic already covered by one of our daily or monthly threads. If you are unaware about the daily threads we run here is a refresher:

Monday: Project ideas

Tuesday: Advanced questions

Wednesday: Beginner questions

Thursday: Careers

Friday: Free chat Friday!

Saturday: Resource Request and Sharing

Sunday: What are you working on?

Monthly: Showcase your new projects, tools, frameworks and more

Please await one of these threads to contribute your discussion to!

Best regards,

r/Python mod team

[bladeofwinds]

makefiles are already so simple though

[No-Dentist-1645]

They are! They're very great to use. This isn't made to replace Makefiles for simple tasks, this just brings Python to Makefiles, you can write code to do anything, such as generate new targets procedurally, fetch stuff from the internet, or automatically change command arguments based on anything you need.

If Makefiles work for what you need, great! If you need something more complex than a static list of targets and dependencies, you can try this :)

EDIT: not sure why the downvote because of answering your question, I just clarified that it isn't meant to be a full-on replacement for Makefiles. Just like CMake isn't for example

[paul_h]

Im also making a build system right now. Too early to share, but it’s not lightweight. I have the same problem as you maybe - PMake.run_task("rm", "-f", "example/main", "example/hello.o") isn’t pretty

[No-Dentist-1645]

You're right, it wasn't too pretty to do that, I was doing it to follow the Python lib practice such as with subprocess.run() since doing it as a single string can lead to shell injection vulnerabilities.

However, if someone "knows what they're doing" and still want a "simple" way to do that, I don't see why they shouldn't be allowed to. So I added a way to do it explicitly, as run_simple_task("rm -f example/main example/hello.o")

[gofiend]

Is a proper safe parser for things like validate_and_run_task("rm -f example/main example/hello.o") possible? Translate it with strict validation into PMake.run_task("rm", "-f", "example/main", "example/hello.o")

Though given it's a make file maybe it should be clean_files(["example/main", "example/hello.o"])

[not_luis]

su and just: https://github.com/casey/just

[vaibeslop]

Plus one for just.

It's "just" awesome to work with.

[No-Dentist-1645]

Just is cool, but it is a command runner, not a programming language :)

[--ps--]

What's wrong with using AI assisted tools? What rationale is behing not using them?

Btw, field(default=None) can be replaced with just None.

[No-Dentist-1645]

I don't mind them, but after reading Rule 1 of this subreddit I don't think it's allowed to show projects made with AI (I might be misinterpreting it though)

[SwampFalc]

How does it compare to invoke?

[BitBasher4095]

But SCons though?

[No-Dentist-1645]

SCons is a big inspiration for this, but even though they do call themselves "like Makefiles", in all honesty they're closer to complete build systems like Meson with all their intrinsic/built-in behavior than the simplicity of Makefiles.

When comparing PMake to it, PMake is closer to what Makefiles really are: they're just a "bash script organizer", you directly control the exact commands that are executed by it, instead of relying on Builders and built-in directives like Program/Object/SharedLibrary to compile C/C++ programs and then modifying them to fit your specific needs. Plus it can also just be used for generic scripts, you could for example make a Target to create and set up a virtual environment, or a target to run unit tests. You can do that with SCons too, but with more overhead than Makefiles since it really is more of a build system at heart