(Hmm, would this (sub?)thread be a good candidate for alt.unix.geeks?
Leaving Newsgroups: as-is, but I don't subscribe to comp.lang.python.)
On 2026-03-04, Lawrence D’Oliveiro wrote:
> On Wed, 4 Mar 2026 14:09:58 -0700, Peter Flass wrote:
>
>> On 3/4/26 13:29, Carlos E.R. wrote:
>>>
>>> On 2026-
Please use an appropriate subject. That makes it easier to filter that
noise.
--
https://mail.python.org/mailman3//lists/python-list.python.org
Hi all,
I've been working on a Python script to perform bulk DNS lookups (A, MX, TXT
records) for a list of ~500 domains to audit SPF/DKIM/DMARC configurations.
Currently I'm using `dns.resolver` from dnspython with ThreadPoolExecutor:
```python
import dns.resolver
from concurrent.futures impor
On 3/4/26 17:35, Lawrence D’Oliveiro wrote:
On Wed, 4 Mar 2026 14:09:58 -0700, Peter Flass wrote:
On 3/4/26 13:29, Carlos E.R. wrote:
On 2026-03-04 21:01, Ted Nolan wrote:
.
A man with one clock knows what time it is. A man with two is
never quite sure...
Experimental science would not a
In article <[email protected]>,
Michael F. Stemper wrote:
>On 18/12/2025 12.00, Richard Kettlewell wrote:
>> Peter Flass writes:
>>> I comment *A LOT*. When I had to go back and revisit some very old
>>> code, I wished I had commented more. I've almost never looked at a
>>> program
On 18/12/2025 12.00, Richard Kettlewell wrote:
Peter Flass writes:
I comment *A LOT*. When I had to go back and revisit some very old
code, I wished I had commented more. I've almost never looked at a
program and said "I wish it had fewer comments."
Regrettably, I’ve encountered plenty of com
>
> The bad news? I knew enough German to be able to tell that the two paired
> comments sometimes disagreed on what was being done or how it was done.
>
> That's pretty funny.
--
https://mail.python.org/mailman3//lists/python-list.python.org
On 04/03/2026 21.29, Carlos E.R. wrote:
[...]
A man with one clock knows what time it is. A man with two is never
quite sure...
Experimental science would not agree.
Well, experimental science would *exactly* agree...
That's why it provides "uncertainty", together
with the experimental resu
On 3/4/26 13:29, Carlos E.R. wrote:
On 2026-03-04 21:01, Ted Nolan wrote:
In article <[email protected]>,
Michael F. Stemper wrote:
On 18/12/2025 12.00, Richard Kettlewell wrote:
Peter Flass writes:
I comment *A LOT*. When I had to go back and revisit some very old
code, I w
On 2026-03-04 21:01, Ted Nolan wrote:
In article <[email protected]>,
Michael F. Stemper wrote:
On 18/12/2025 12.00, Richard Kettlewell wrote:
Peter Flass writes:
I comment *A LOT*. When I had to go back and revisit some very old
code, I wished I had commented more. I've almo
On Wed, Mar 4, 2026 at 2:11 PM Ted Nolan
wrote:
>
> In article <[email protected]>,
> Michael F. Stemper wrote:
> >On 18/12/2025 12.00, Richard Kettlewell wrote:
> >> Peter Flass writes:
> >>> I comment *A LOT*. When I had to go back and revisit some very old
> >>> code, I wishe
On 04/03/2026 21:14, Piergiorgio Sartor wrote:
On 04/03/2026 21.29, Carlos E.R. wrote:
[...]
A man with one clock knows what time it is. A man with two is never
quite sure...
Experimental science would not agree.
Well, experimental science would *exactly* agree...
That's why it provides "u
12 matches
Mail list logo
