bjorney

You should look at how OPs example works first maybe

The python interpreter isn’t parsing comments, the add() function is just getting the current line number from the call stack context, and using a regex to spit out the numbers to the right of the “#” on the current executing line of the source code.

Do you stay away from C++ too? You can do this there too

https://en.cppreference.com/w/cpp/utility/source_location/line

This stuff is normally used for creating human readable error messages. E.g. printing the line of your code that actually set off the exception

The add function in the example above probably traverses the call stack to see what line of the script is currently being executed by the interpreter, then reads in that line in the original script, parses the comment, and subs in the values in the function call.

This functionality exists so when you get a traceback you can see what line of code triggered it in the error message

You can just point your domain at your local IP, e.g. 192.168.0.100

Maybe a riff on lutris? Not sure why though

Not with 64gb ram and 16+ cores on that budget

English is not my native language, and I don’t understand what “Have taken up farming.”

It means they aren’t developing software anymore because they are growing vegetables instead

Actually, I‘m just excluding companies like yours because they are making way too much revenue on the basis of FOSS without giving back

You don’t know anything about my company? You don’t know what proportion of FOSS vs proprietary software we use, nor how much we give back lol.

It would completely break the locked down proprietary software model and break walled gardens wide open.

This is very pie in the sky. Your license idea only penalizes small to medium sized businesses. Alphabet’s 1% would just go to Chromium/AOSP, and Meta’s 1% would just go to React/Torch

You are probably better off setting up a non-profit and running traditional license fees through it into your payment union then. I can’t emphasize how much of a non-starter 1% of revenues is for any business (it’s my company’s entire IT budget, including salary) - you are basically just saying “personal use only” with more words.

1% is an exorbitant amount of money, and more than most businesses would be able to donate via credit card, so they would still have to reach out to repository owners for banking info

They would have to get in touch to figure out how to pay 1% either way, no?

“how dare they use the right tool for the job without taking the time to learn how to do it sub optimally first”

To elaborate a bit more, there is the MySQL resource usage and the docker overhead. If you run two containers that are the same, the docker overhead will only ding you once, but the actual MySQL process will consume its own CPU and memory inside each container.

So by running two containers you are going to be using an extra couple hundred MB of RAM (whatever MySQL’s minimum memory footprint is)

it won’t necessarily take twice the resources of a single mysql container

It will as far as runtime resources

You can (and should) just use the one MySQL container for all your applications. Set up a different database/schema for each container

This has already been patched on all 64 bit OSes though - whatever 32 bit systems are still in existence in another 15 years will just roll their dates back 50 years and add another layer of duct tape to their jerry-rigged existence

But running those pip commands you mentioned is only going to affect what version gets installed initially.

I don’t follow. If my package-lock.json specifies package X v1.1 nothing stops me from manually telling npm to install package X v1.2, it will just update my package.json and package-lock.json afterwards

If a requirements.txt specifies X==1.1, pip will install v1.1, not 1.2 or a newer version. If I THEN install package Y that depends on X>1.1, the pip install output will say 1.1 is not compatible and that it is being upgraded to 1.2 to satisfy package Y’s requirements. If package Y works fine on v1.1 and does not require the upgrade, it will leave package X at the version you had previously installed.

Would that just create a list of the current packages/versions

Yes, and all downstream dependencies

without actually locking anything?

What do you mean? Nothing stops someone from manually installing an npm package that differs from package-lock.json - this behaves the same. If you pip install -r requirements.txt it installs the exact versions specified by the package maintainer, just like npm install the only difference is python requires you to specify the “lock file” instead of implicitly reading one from the CWD

pip also has lock files

pip freeze > requirements.txt