I like the format, the "here is a problem and libraries that solve it/here is a library here is what problems they solve" is a good format. How opensouce can be/should be funded would be interesting to hear.
One potential pitfall when switching between tox and Nox: with tox, you have to be explicit and use "setenv" to make environment variables known to commands; not so with Nox.
Thanks for another great video. With regards to video subject wishes, I wish for: 1. Anything in this category (project management, basically all things _around_ the project). They are highly appreciated! 2. A video on the deep dark magic that makes attrs tick, might be fun, but maybe not as much your style? 3. Your takes on any controversy or hot new things. I find you well informed and pleasently objective.
Finally got around to watching this one! Wonderful content, as usual. Guess I'm gonna have to read your noxfiles to see how you integrate with GH Actions matrix... BTW, I'm still waiting on that 3hr video!
It's worth the wait. Now I'm curious to see how you use Just as well. I'm a Make curmudgeon and would love to see some examples where Just makes things easier than Make.
The main issues with Make are that there’s no “make”, there’s at least two (GNU & BSD), it’s not very cross-platform, and make is a BUILD tool that we abuse as a command runner but we end up righting it (c.f. .PHONY). Just solves all of those and adds some really nice features that are focused on it being a command runner.
Do we have anything to test my package with all the dependencies versions and run tests for them so i will know what versions is supported by my package? How can i know what is minimum and maximum version for each dependencies of my package? BTW huge thanks for your videos
Practically speaking, to find them you have to test it. Of course, that can get quite complex with an increasing number of dependencies. I would suggest the setup I show at the end of the video and then do a bisection/binary search (try the oldest available, then the middle-oldest, etc).
I like the format, the "here is a problem and libraries that solve it/here is a library here is what problems they solve" is a good format. How opensouce can be/should be funded would be interesting to hear.
oh gosh I sure hope someone figures that out too! ;)
One potential pitfall when switching between tox and Nox: with tox, you have to be explicit and use "setenv" to make environment variables known to commands; not so with Nox.
Yes, tox is generally stricter WRT sanitation. Most of the measures are opt-out while Nox tends to be opt-in.
Hynek your content is always fantastic!
Thanks for another great video. With regards to video subject wishes, I wish for:
1. Anything in this category (project management, basically all things _around_ the project). They are highly appreciated!
2. A video on the deep dark magic that makes attrs tick, might be fun, but maybe not as much your style?
3. Your takes on any controversy or hot new things. I find you well informed and pleasently objective.
I was afraid 1 and 3 are gonna be audience hits. 😅 thanks for the input and the kind words!
Finally got around to watching this one!
Wonderful content, as usual. Guess I'm gonna have to read your noxfiles to see how you integrate with GH Actions matrix...
BTW, I'm still waiting on that 3hr video!
Probably gonna happen when I decide to produce a “5 mins max” video… which is right now. 😳
It's worth the wait. Now I'm curious to see how you use Just as well. I'm a Make curmudgeon and would love to see some examples where Just makes things easier than Make.
The main issues with Make are that there’s no “make”, there’s at least two (GNU & BSD), it’s not very cross-platform, and make is a BUILD tool that we abuse as a command runner but we end up righting it (c.f. .PHONY). Just solves all of those and adds some really nice features that are focused on it being a command runner.
My first thought was the Dr Seuss book Fox in Socks.
Do we have anything to test my package with all the dependencies versions and run tests for them so i will know what versions is supported by my package? How can i know what is minimum and maximum version for each dependencies of my package?
BTW huge thanks for your videos
Practically speaking, to find them you have to test it. Of course, that can get quite complex with an increasing number of dependencies. I would suggest the setup I show at the end of the video and then do a bisection/binary search (try the oldest available, then the middle-oldest, etc).
"Back when Twitter was still fun!" Silly Hynek, Twitter was never "fun".
My meme made it into a Hynek video. Am I famous now?
You are, but I couldn’t find it so I had to… counterfeit it. Forgive me and rest assured it’s handmade, artisanal, with no AI!