Search results

Greetings, programs ๐Ÿ’พ
I've got the honor to present you the match you all have been waiting for: The final of the 2025* Programming Languages World Cup:
vs.

*yes, yes I know, but we started in 2025. Will start the next one earlier, so it doesn't get confusing again.

0
0
0
0
0

RE: f.cz/@vitexsoftware/1159560899

Ono se dalo ฤekat ลพe to jednou vznikne. Neplรกnuju sice teฤ vลกechno co jsem napsal za poslednรญch 10 let pล™epsat do pythonu, ale zas to dรกvรก svobodu nฤ›jakรฉ novรฉ projekty v zaฤรญt

0

Je zde dobrรก sprรกva pro milovnรญky jazyka kteล™รญ majรญ v plรกnu mรญt co do ฤinฤ›nรญ s ekonomickรฝm systรฉmem .

Na vฤ›domรญ se tรญmto dรกvรก ลพe u pล™รญleลพitosti 60000 instalacรญ jejรญ starลกรญ PHP sestล™iฤky vznikla za laskavรฉ podpory p. Radka Vymazala (co si vymazal svลฏj mastodon, takลพe zde na nฤ›j nemลฏลพu odkรกzat)

Zatรญm se jednรก o prototyp nicmรฉnฤ› v plรกnu je jejรญ brzkรฉ zaฤlenฤ›nรญ do produktลฏ kterรฉ pracujรญ s flexibรญฤkem. Veลกkerรฉ kontribuce budou pล™ivรญtรกny ovacemi.

pypi.org/project/python-abrafl

0

I'm making a pattern for a bouldering chalkbag in Inkscape, and I was laying out the pages so that they would tile for my printer by hand, and thought to myself "this is going to take *minutes*, I bet that in only a few dozen hours I can write a script to do this automatically". So I wrote my first Inkscape extension.
It overlaps pages with optional registration marks. The extension, and the chalkbag pattern are up on my codeberg.
codeberg.org/stib/stibs_inksca

A fabric pattern layed out on A4 pages. Each one is overlapped a bit, with a cross and circle in the corner.
0
0

re: morshutalk-v2 dev thread

Today's goal is to figure out audio transcoding in Python so I can always have this thing output a smaller file for uploading elsewhere. I don't want to rely on subprocess because that makes things too OS-specific (I at least want to know this works on Windows and Linux) and I don't want to deal with any kind of external calls that I can't guarantee will stay the same between systems or (major) versions.

I at least want to be able to output to one other audio format - and if I can get away with feeding the encoder the bytearray (and thus not writing a wav file), even better. Target bitrate is going to be "good enough for speech" (so Low) and sample rate is going to also be "good enough for speech" (still low).

I did wonder if it'd be possible to use a different bit-depth, but after digging into things yesterday it looks like Python doesn't like that - unless I went from 16-bit to 32-bit, but that's way more than I need and thus a much larger file than warranted.

Anyways. Y'all will find out what ends up happening today.

#MorshuTalk_v2 #Python

re: morshutalk-v2 dev thread

Blessed be, someone has continued opuslib since it was deprecated forever ago, so I'll be working directly with opuslib_next for all of my opus output needs. Audio will at the very least be encoded both as the original wav file in addition to the OGG opus audio file. At least, assuming I can't find a higher-level option that's actively maintained.

Since I'll be working with opuslib more closelier (likely) it'll be More Annoying (TM) but a. it means I get to Learn python more gooder and 2. I'll get to figure that all out.

I think I'll abandon the idea of using anything but a 16-bit depth for the audio output - I can easily get away with a 22050 Hz sample-rate since we're talking voice lines, and Opus or whatever is going to compress things down a fair bit as well. We're also talking audio that's probably not much longer than 15 seconds barring the occasional jank, so an ever so slightly larger file because I can't be bothered to figure out narrower bit-depths is fine.

I'm still borrowing the original phoneme array since I don't want to sift through the original speech again to track down any possible improvements just yet. It honestly might be one of the few original bits that are exactly (or extremely) close to the original morshutalk, outside of the Morshu class.

I do want to tweak things to let him say numbers since g2p doesn't handle that eng -> eng-arpabet conversion at ALL (understandably so) so I need to figure out separating those if they're ever next to another character, and then convert the individual numerals into text (only covering 0 through 9, sorry he'll sound weird if you try to make him say 40 or whatever), which will then be handled properly by g2p.

No significant progress today other than finding opuslib_next, but that does give me a lead to dig into for encoding purposes. Whether I stick to using opuslib_next directly or use a higher-level system that's also cross-platform friendly IDK, but that'll come with time.

#MorshuTalk_v2 #Python

0

re: morshutalk-v2 dev thread

Thinking about it some more, I might try to just always encode the audio into either ogg-opus or AAC for size (and fediverse compatibility) reasons. Making sure the sample rate, bit-depth, and bitrate target are set correctly is going to be Annoying but worthwhile since the purpose of this is to hook up to a markov-chain system where you can intercept (?) the generated text to add the audio to the post as an attachment.

Which is prooobably going to mean gently modifying Mame-Brot to make morshutalk-v2 calls within itself to post thataway. Eh, later me problem. Only matters once I have this up and functional consistently.

edit: unrelated to this but oh thank fuck, that old g2p_en library that the OG morshutalk used is just a weird fork of the actual g2p maintained by NRC-ILT. The only change I'd need to do (other than probably re-doing the phonemes from Morshu's lines) would be to manually invoke the language I/O to be eng and eng-aprabet, respectively.

Well, that's one major library hurdle dealt with.

#MorshuTalk_v2

re: morshutalk-v2 dev thread

Today's goal is to figure out audio transcoding in Python so I can always have this thing output a smaller file for uploading elsewhere. I don't want to rely on subprocess because that makes things too OS-specific (I at least want to know this works on Windows and Linux) and I don't want to deal with any kind of external calls that I can't guarantee will stay the same between systems or (major) versions.

I at least want to be able to output to one other audio format - and if I can get away with feeding the encoder the bytearray (and thus not writing a wav file), even better. Target bitrate is going to be "good enough for speech" (so Low) and sample rate is going to also be "good enough for speech" (still low).

I did wonder if it'd be possible to use a different bit-depth, but after digging into things yesterday it looks like Python doesn't like that - unless I went from 16-bit to 32-bit, but that's way more than I need and thus a much larger file than warranted.

Anyways. Y'all will find out what ends up happening today.

#MorshuTalk_v2 #Python

0

<code>morshutalk-v2</code> dev thread I guess?

(Larger updates are prob going to be blog posts once things are off the ground and things are Allegedly Functional, but for now this'll do)

Today's "progress" (if I can even call it that) mostly just consists of getting the absolute basics down for how to structure things, refreshing myself on how to Python, and also pulling over the tiny bits of code that won't be changed from morshutalk-output (being the .wav file write). Still need to look into alternatives for a bunch of the packages, I want to try and use stuff that's up-to-date and doesn't rely on deprecated features like audioop.

I think I'm only going to have morshutalk-v2 support outputting the raw wav file, and/or convert it to opus (in an ogg container) or, failing that, aac. Whether I'll have it always do both or not IDK, it depends on whether I can skip writing the wav file and can pass the appropriate bytearray into the encoder.

On Linux that's fairly easy so long that opusenc is installed, since I can just use subprocess to do a system call within the python code. But I really want to try and avoid doing anything like that - if I can get a mostly-straightforward transcode into opus or aac or whatever I'd be much happier, I want to try and avoid any system-level dependencies if possible. Mostly as an exercise in portability, and also to avoid any weirdness that'd come with versioning outside of my control.

But "technically functional" is better than "not functional" at least. The actual morshu-v2 class and all that doesn't exist yet, since that all has to wait for me to identify what libs are viable replacements for what the OG version of morshutalk uses, and what I can wrap into native Python code (if possible and if not painful to do so).

#MorshuTalk_v2 #Python

0
0

New temp pinned post:

I am looking for a job!

Info on my professional website.

NB. The website is my contracting/freelance site, but in the Netherlands, I would have a regular employment job.

mah-rye-kuh.nl/en/hire-me/

0
0
0
0

The biggest PEP:

โฏ wc -w peps/pep-*.rst | sort --reverse | head -10
1854017 total
17128 peps/pep-0000.rst
14184 peps/pep-0817.rst
13436 peps/pep-3156.rst
13099 peps/pep-0773.rst
12978 peps/pep-0484.rst
12910 peps/pep-0622.rst
12606 peps/pep-0642.rst
12400 peps/pep-0810.rst
11994 peps/pep-0703.rst

(PEP 0 is the autogenerated index page)

peps.python.org/pep-0817/

0
0

Hello data fans!

Some newish API things on the PEPs website.

release-cycle.json is summary of Python x.y releases from 1.6: support status, release PEP, release manager, important dates.

python-releases.json also has info for each x.y.z version: release date and whether actual/planned.

release-schedule.ics is an iCal, especially useful if you're a release manager and want to plan [your life around] releases.

More details: peps.python.org/api/

0
0

๐Ÿšจ New Episode Alert! ๐Ÿšจ

Episode 7: The Definitely Not 3 Months Too Late DjangoCon US 2025 Recap ๐Ÿ˜‰

djangobrew.com/episodes/185391

Adam and Sangeeta finally get around to recapping 2025 in Chicago, then immediately derail into lightning talks, Labubus, and deeply questionable horror movie discussions ๐Ÿ‘ป

Was this episode overdue? Yes ๐Ÿ˜ฌ
Was it worth the wait? Also yes ๐Ÿ˜Ž

Now streaming on your favorite podcast app ๐ŸŽง

0
0
0
0
0

it feels hard to talk about how to write websites that feel manageable to maintain with like 0.5% of my brain because there are a thousand tiny and not always logical decisions like "use bash scripts to run my local dev server, because then it's `bash scripts/run.sh` no matter what programming language the project is in"

or "refuse to use any database other than SQLite because I had a bad experience operating Postgres once and I feel more comfortable with sqlite"

0
0
0
0
0
0
0

How does one spelunk history? I see that breakpoint() was added all the way back in 3.7, but hasn't been improved on at all.

I can't be the first person who wanted to do "breakpoint(x,y)" to start the debugger and immediately print out the values of x and y, instead of making me type each in the debugger every time I got to this spot.

Where can I find the discussion of what breakpoint() should and should not be able to do?

0
Four books shown in a line. Beneath each of the books is its title:

- Naming & Logic with Scheme
- Naming & Logic with Wisp
- Python to Guile Scheme
- Ein-Wรผrfel-System 2.6

Below each title is a symbol of a stack of books next to a buy-link and the ISBN.
0
0
0
0
0
0

There's PyConDE/PyConIT community voting going on this weekend.

If you've visited one of those conferences in the last years, you can vote (even if you can't come this time). By voting you can influcence which talks will be available for you to watch online later in the year - and you get a good overview on what's hot this year.

๐Ÿ‡ฉ๐Ÿ‡ช 2026.pycon.de/blog/community-v

๐Ÿ‡ฎ๐Ÿ‡น 2026.pycon.it/en/voting-info

0