logging_strict

joined 11 months ago
[–] logging_strict@programming.dev 3 points 4 days ago* (last edited 4 days ago)

Just got back from talking with our team. The senior coder in charge of emojis in usernames is currently upgrading the windmills in the uk, having been able to enhance efficiency by 0.001%. Wow! Thats 14 Mega tons of CO2 removed from the atmosphere every year!

Will take the weekend to get commercial Fusion energy rolled out and right after that will address your issue. Which i'm sure many other users will be thankful you brought to our attention. And luckily had the right man for the job on staff. He's amazing, capable, enthusiastic, and eager to help.

"I admire your creativity. Will talk with our team, get their feedback, and timeline. See when can add support for emojis in usernames"

[–] logging_strict@programming.dev 5 points 4 days ago (3 children)

Hmmm ... Thought it was agreed to not to say the quiet part out loud eh?

No one likes being insulted ESPECIALLY when it's true.

This is why we praise them and spin every statement in a positive light.

i'm opposed to Grandma asking for IT support

Grandma gets a smartphone

[–] logging_strict@programming.dev 1 points 4 days ago (1 children)

They live along with us.

  • a bulldog gets onto a treadmill

  • a dog is trained to press buttons on the floor to express their desires

  • AI is used to decipher an animals language meaning and speech recognition

  • Koko the gorilla using celebrities to do marketing and guarantee TV time and our attention.

All these things are animals using tech.

 

In a requirements-*.in file, at the top of the file, are lines with -c and -r flags followed by a requirements-*.in file. Uses relative paths (ignoring URLs).

Say have docs/requirements-pip-tools.in

-r ../requirements/requirements-prod.in
-c ../requirements/requirements-pins-base.in
-c ../requirements/requirements-pins-cffi.in

...

The intent is compiling this would produce docs/requirements-pip-tool.txt

But there is confusion as to which flag to use. It's non-obvious.

constraint

Subset of requirements features. Intended to restrict package versions. Does not necessarily (might not) install the package!

Does not support:

  • editable mode (-e)

  • extras (e.g. coverage[toml])

Personal preference

  • always organize requirements files in folder(s)

  • don't prefix requirements files with requirements-, just doing it here

  • DRY principle applies; split out constraints which are shared.