100% agree – dealing with 5 or more platforms for discussion groups is a
nightmare, and I tend not to follow any of them as closely for that reason.
From: Skip Montanaro
Date: Friday, July 15, 2022 at 9:26 AM
To: Petr Viktorin
Cc: python-dev@python.org
Subject: [SPAM] [Python-Dev] Re: Switchin
On 2/22/21, 4:06 PM, "Antoine Pitrou" wrote:
On Mon, 22 Feb 2021 19:50:43 +0000
Rob Boehne wrote:
>
> The other thing that crept into this thread was the mention of test that
intermittently fail.
> That's a huge problem because it suggest
On 2/22/21, 1:39 PM, "Steve Dower" wrote:
On 2/22/2021 5:18 PM, Matthias Klose wrote:
> On 2/21/21 1:13 PM, Victor Stinner wrote:
> Document what is supported, be inclusive about anything else. Don't make
a
> distinction yet between legacy and upcoming new architectures.
I
On 10/5/18, 10:33 AM, "Python-Dev on behalf of Michael Haubenwallner"
wrote:
>
>... I build everything myself, using xlc
>(gcc introduces the need for a GNU RTE, e.g., glibc).
Using gcc does *not* require to use glibc or even GNU binutils at all.
Except for gcc's own
Why would a VIM build refer to the export file for python?
From: Python-Dev on behalf
of "WILSON, MICHAEL"
Date: Friday, July 27, 2018 at 10:27 AM
To: "python-dev@python.org"
Cc: "WILSON, MICHAEL"
Subject: [DLFILTER] [Python-Dev] Exporting Python functions on AIX
All,
My excuse if this is n
On 5/13/18, 12:44 PM, "Python-Dev on behalf of Christian Heimes"
wrote:
On 2018-05-13 06:57, Serhiy Storchaka wrote:
>
https://github.com/python/cpython/commit/1e2ec8a996daec65d8d5a3d43b66a9909c6d0653
> commit: 1e2ec8a996daec65d8d5a3d43b66a9909c6d0653
> branch: master
> a
, and and the language itself. In that vein,
I treated them seriously and hopefully gave you useful feedback.
Thanks,
Rob Boehne
From: Python-Dev on behalf
of amar via Python-Dev
Reply-To: amar
Date: Tuesday, April 3, 2018 at 10:42 AM
To: "python-dev@python.org"
Subject: [Python-Dev
problems,
I’m going to submit pr’s in a trickle, as time permits. I’m picking HP-UX
because it’s probably the most obscure thing we use, and likely would take the
most effort.
From: Lukasz Langa
Date: Wednesday, December 6, 2017 at 11:45 AM
To: Rob Boehne
Cc: "python-dev@python.org"
hard to convince management that we shouldn’t create technical
debt by maintaining patches to all the tools we use, and that we should get
these changes accepted into the upstream repos.
Could someone have a look at this PR and possibly merge?
Thanks,
Rob Boehne
Victor,
Thanks - I will comment on the issue WRT backporting the fix.
If you have particular issues you’d like me to look into, just point me in
the right direction.
Thanks,
Rob
On 6/30/17, 2:29 AM, "Victor Stinner" wrote:
>Hi Robb,
>
>2017-06-29 23:34 GMT+02:00 Rob Boe
and I¹d
like to see it applied to 3.6. I¹m happy to create a PR with a
cherry-picked commit, and/or test.
Rob Boehne
Senior Software Architect | Datalogics, Inc.
+1.312.853.8351 | r...@datalogics.com
<mailto:j...@datalogics.com>
datalogics.com <https://www.datalogics.com/> | blogs.da
11 matches
Mail list logo
