gitz
wavemap
gitz | wavemap | |
---|---|---|
8 | 4 | |
30 | 6 | |
- | - | |
6.8 | 5.7 | |
about 2 months ago | 3 months ago | |
Python | Python | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
gitz
-
Managing secrets like API keys in Python - Why are so many devs still hardcoding secrets?
When I develop a big feature, I do it on a private branch, and then I commit and push an "anonymous" commit (using this) whenever I have made any progress.
-
An alias that has saved me hours since I created it yesterday
where git st is here (a lot like git status.)
-
GitHub's Missing Merge Option
No, there's no reason to preserve commit messages you used during development.
When I am developing, I make many tiny commits with an automatically generated title ('Modify util/files.py') each time my tests pass, or really, when I do anything of value. (I use `git-infer`: https://github.com/rec/gitz/blob/master/git-infer)
This makes it impossible for me to lose work, and acts like a coarse-grained undo for me, where I can quickly move back and forth between spots that the tests worked if I decide I'm going the wrong way, or create a new branch, move back a bit, and make some changes and compare.
_Before anyone sees this code_ I rebase it down to a logical sequence extremely-carefully named and organized commits. (The word "manicured" has been used more than once.)
As I go through code review, I make tiny commits and at the end, rebase them into my carefully-named commits.
I create at least five commit IDs for each final commit I created. No one wants to see these.
I spend considerable time organizing everything so just the information you need to see is in the final commits. All the information should be there.
-
What one thing would you improve about Git?
I have a truly evil command in my gitz package https://github.com/rec/gitz called git adjust.
-
Eli5: Why do so many people like to use the terminal instead of a good client?
I have a bunch of git utilities to do common chores, but more, I tend to stack up a lot of commands at once in the command line separated by &&.
-
Why is git pull broken?
This isn't just academic - it affects every git tool. I have a collection of git utilities, fairly high quality, but a lot of my favorite ones don't work over merge commits, not because I was lazy but because I simply couldn't figure out a way to do it that made sense in every case.
- Does format() method returns a list?
wavemap
-
44100 VS 48000
You can even memory-map audio files so they look like huge arrays of numbers - if you don't use 24-bit audio.
- Does format() method returns a list?
-
Formats for very large uncompressed audio files?
But my guess is that I will probably implement RF64 first, because I can probably tweak my existing parsing code to do it with little stress.
-
CMV: 32-bit float is the best and final audio recording format
Most of the details of the format are here and the code to handle the offsets is here.
What are some alternatives?
Git - Git Source Code Mirror - This is a publish-only repository but pull requests can be turned into patches to the mailing list via GitGitGadget (https://gitgitgadget.github.io/). Please follow Documentation/SubmittingPatches procedure for any of your improvements.
audio-reactive-led-strip - :musical_note: :rainbow: Real-time LED strip music visualization using Python and the ESP8266 or Raspberry Pi
safer - ๐งท A safer writer ๐งท
xmod - ๐ฑ Turn any object into a module ๐ฑ
vl8 - ๐ Perturbed audio ๐
git-push-update - Push with "server-side" merge or rebase
spleeter - Deezer source separation library including pretrained models.
editor - ๐ Open the default text editor ๐