People who use Beautiful Soup for #Python screenscraping and various data projects:
https://groups.google.com/forum/?fromgroups#!topic/beautifulsoup/-w7TDFkaPTg
https://groups.google.com/forum/?fromgroups#!topic/beautifulsoup/aNC2TBR7QHY
On the upcoming sunset of Python 2 support, and of Beautiful Soup's 3.x series (switch to bs4)
@arkedos PEP 7 is the equivalent style guide for C.
#todayILearned that, when searching in Firefox's tab bar, you can prefix your search with `%` to search exclusively in the titles of open tabs.
Maybe everyone else already knew this, but I didn't—and I have the feeling that it will *dramatically* increase the number of open tabs I have at any given time.
#plaintext email etiquette question:
When I'm replying to a thread with multiple participants, is there a standard way to indicate who I am quoting?
For example, in the exchange below, is there a good/standard way to attribute the first quote to Alice and the second to Bob?
> Foo is better
> Bar is better
I agree with Alice that foo is the way to go.
CC: @sir, resident plaintext email expert/evangelist
Great software documentation has these key things (not necessarily split like this):
User's Manual: How to use the software and all its features in enough detail to stand alone for normal use, including basic troubleshooting.
Service Manual: The broad design of the software and how to install, configure, upgrade, and otherwise maintain it, including advanced troubleshooting.
Programmer's Manual: Design details, APIs, and internals needed to modify the software or write code that works with it.
Now that we're all rested from the holidays, time for you all to sign up for some fun activities: https://fosdem.org/2020/news/2019-12-31-call-for-volunteers/ Jokes aside, it would be literally impossible to make FOSDEM happen without all the wonderful people who volunteer, so thank you :) !
@design_RG Thanks for working on this! Sorry that it doesn't seem to have had a happier ending (though there's always hope)!
@design_RG See this thread: https://mastodon.technology/@pganssle/103199195138668923
It seems unlikely we'll be unblocked.
@design_RG This is actually why I switched to qoto.org. They seem to want to defederate from anyone who doesn't believe in defederating from gab et al.
It's a bit sad and honestly one of the most offputting parts of the fediverse for me.
@bitecode Haha, definitely don't use this.
@freemo Depends on what you are backing up. A few seconds in most cases, but if you hit something with hundreds of thousands of little files and directories it can be minutes or more (in my case some deduplicating backups).
In my use case backing those up isn't that useful anyway, so a way to exclude them is probably a more fruitful way to speed up my backups.
I did some basic profiling and I think the multi-threading behavior is actually not buying me much, because a lot of the time is spent doing the zip encoding.
Not sure if there is a simple way to parallelize that or if it's even worth doing.
I soft-launched this a few weeks back, but here is my most polished (i.e. not very) @rustlang project to date: metadata-backup, a tool for backing up your file system metadata.
Contributions welcome!
matrix the message protocol or whatever
@CobaltVelvet@octodon.social I don't understand where you are coming from here. The blog post is about federation vs. Signal's model of tightly coupled servers and clients.
The blog post seems to indicate that they are also looking into a more P2P model where the client and server are one thing (very encouraging in my opinion).
Hardly seems like, "We'll die on the federation hill.", but maybe I'm missing some subtext?
@toast Yeah, well that's another way that Python 2 has been increasingly already dead. The latest releases of matplotlib, ipython, Django and pandas haven't supported Python 2 for a long while.
Python's killer feature for me is the third party ecosystem. Even if core python delayed Python 2's death officially, are you really better off with frozen versions of all your dependencies?
@toast Personally I think the "end of life" date was a pretty arbitrary epoch anyway. Management types like firm dates and deadlines so they were given one.
In reality, Python 2 has been increasingly unsupported over the course of a few years. Some distros will probably make half-hearted efforts to patch it for a few years hence.
@toast I suspect we'll do things like close all the open Python 2-only bugs as wontfix as part of the wind-down. After January 2020 release manager has to approve anything that goes into the release. I can't speak for him, but I think the assumption is that we'll only be merging bugs introduced since the last release.
Programmer working at Google. Python core developer and general FOSS contributor. I also post some parenting content.