On Thu, May 23, 2019, 12:17 AM Ivan Pozdeev via Python-Dev <
python-dev@python.org> wrote:
> On 22.05.2019 23:52, Steve Dower wrote:
> > On 22May2019 1309, Ivan Pozdeev via Python-Dev wrote:
> >> As someone whose job is to diagnose and fix problems with running
> software:
> >> Are there patches i
gt;
>
> On Mon, Oct 8, 2018 at 11:59 PM Ray Donnelly wrote:
>>
>> Hi,
>>
>> We ran into an issue on the Anaconda Distribution recently where we
>> added libarchive-c to conda-build (so we can un-compress more source
>> archive formats than tarfile supports)
tures. Would CPython be interested in
an attempt to upstream this?
Is it documented anywhere that objdump is needed to load some
extension modules on Linux?
Best regards,
Ray Donnelly,
Anaconda Inc,
___
Python-Dev mailing list
Python-Dev@python.org
MSYS2 has two Python ports, msys2 and mingw-w64. I believe Eric was
referring to the mingw-w64 one?
zlib1.dll in C:\Windows\System32 is a packaging error on the part of
whatever put it there and that is what needs to be fixed here. ISVs
need to stop putting anything in that directory as it leads t
On Fri, May 4, 2018 at 11:00 AM, Antoine Pitrou wrote:
> On Fri, 04 May 2018 00:21:54 +
> Ray Donnelly wrote:
>>
>> Yes, on Windows there's always a python?.dll.
>>
>> macOS is an interesting one. For Anaconda 5.0 I read somewhere (how's that
>&g
On Wed, May 2, 2018 at 6:55 PM, Nathaniel Smith wrote:
> On Wed, May 2, 2018, 09:51 Gregory Szorc wrote:
>>
>> Correct me if I'm wrong, but aren't there downsides with regards to C
>> extension compatibility to not having a shared libpython? Or does all the
>> packaging tooling "just work" withou
On Wed, May 2, 2018, 4:53 AM Gregory Szorc wrote:
> On 7/19/2017 12:15 PM, Larry Hastings wrote:
> >
> >
> > On 07/19/2017 05:59 AM, Victor Stinner wrote:
> >> Mercurial startup time is already 45.8x slower than Git whereas tested
> >> Mercurial runs on Python 2.7.12. Now try to sell Python 3 to
On Wed, Jan 31, 2018 at 3:04 PM, Oleg Sivokon wrote:
> Hello list.
>
> I'll give some background before asking my question in more detail.
>
> I've been tasked with writing some infrastructure code that needs to talk to
> Kubernetes. (Kubernetes is a popular software for managing and automating
On Wed, Jan 31, 2018 at 11:16 AM, Joni Orponen wrote:
> On Wed, Jan 31, 2018 at 9:31 AM, Ray Donnelly
> wrote:
>>
>> We see a 1.1 to 1.2 times performance benefit over official releases as
>> measured using 'python performance'.
>>
>> Apart from a
On Jan 31, 2018 8:31 AM, "Ray Donnelly" wrote:
On Jan 30, 2018 6:47 PM, "Joni Orponen" wrote:
On Tue, Jan 30, 2018 at 6:50 PM, Ray Donnelly
wrote:
> While we're making such macOS-build requests, any chance of building a
> static interpreter too? We
On Jan 30, 2018 6:47 PM, "Joni Orponen" wrote:
On Tue, Jan 30, 2018 at 6:50 PM, Ray Donnelly
wrote:
> While we're making such macOS-build requests, any chance of building a
> static interpreter too? We've been doing that on the Anaconda
> Distribution since the 5.
On Tue, Jan 30, 2018 at 5:42 PM, Chris Barker wrote:
> Ned,
>
> It looks like you're still building OS-X the same way as in the past:
>
> Intel 32+64 bit, 10.6 compatibility
>
> Is that right?
>
> Might it be time for an update?
>
> Do we still need to support 32 bit? From:
>
> https://apple.stac
On Mon, Oct 27, 2014 at 8:54 PM, Steve Dower wrote:
> Greg Ewing wrote:
>> Nick Coghlan wrote:
>>> That assumption will allow MinGW-w64 to link with the appropriate
>>> MSVCRT versions for extention building without anything breaking.
>>
>> If that works, then the same technique should allow CPyth
On Sun, Oct 26, 2014 at 11:52 PM, wrote:
>
> Zitat von Tony Kelman :
>
>> A maintainer has volunteered. Others will help. Can any core developers
>> please begin reviewing some of his patches?
>
>
> Unfortunately, every attempt to review these patches has failed for me,
> every time. In the last
On Sun, Oct 26, 2014 at 10:41 PM, Paul Moore wrote:
> On 26 October 2014 13:12, Tony Kelman wrote:
>> Only cross-compilation and the build system in the above list are relevant
>> to CPython, but I hope I have convinced you, Paul Moore, etc. that there are
>> real reasons for some groups of users
On Sun, Oct 26, 2014 at 2:28 PM, Ray Donnelly wrote:
> On Sun, Oct 26, 2014 at 1:12 PM, Tony Kelman wrote:
>> Thanks all for the responses. Clearly this is a subject about which
>> people feel strongly, so that's good at least. David Murray's guidance
>> in parti
On Sun, Oct 26, 2014 at 1:12 PM, Tony Kelman wrote:
> Thanks all for the responses. Clearly this is a subject about which
> people feel strongly, so that's good at least. David Murray's guidance
> in particular points to the most likely path to get improvements to
> really happen.
>
> Steve Dower:
On Sun, Oct 26, 2014 at 1:45 AM, Steve Dower wrote:
> Ray Donnelly wrote:
>> On Sat, Oct 25, 2014 at 11:44 PM, Paul Moore wrote:
>>> On 25 October 2014 23:22, Chris Angelico wrote:
>>>> On Sun, Oct 26, 2014 at 9:19 AM, Antoine Pitrou
>>>> wrote:
On Sat, Oct 25, 2014 at 11:44 PM, Paul Moore wrote:
> On 25 October 2014 23:22, Chris Angelico wrote:
>> On Sun, Oct 26, 2014 at 9:19 AM, Antoine Pitrou wrote:
>>> My point is that your "Windows build" would not have the same behaviour
>>> as a MSVC-produced Windows build, and so testing it with
On Sun, Oct 26, 2014 at 12:30 AM, Antoine Pitrou wrote:
> On Sat, 25 Oct 2014 19:24:38 -0400
> "R. David Murray" wrote:
>>
>> I know I for one do not generally test patches on Windows because I
>> haven't taken the time to learn how to build CPython on it. Sure, I
>> could test pure python chang
On Sat, Oct 25, 2014 at 10:52 PM, Antoine Pitrou wrote:
> On Sat, 25 Oct 2014 21:10:23 +0100
> Ray Donnelly wrote:
>>
>> This is the second time you've used the vacuous "culture on Windows"
>> argument, now with an added appeal to (vague) authority.
On Sat, Oct 25, 2014 at 6:13 PM, Steve Dower wrote:
> (Apologies for the short reply, posting from my phone.)
>
> "MSVC can continue
> to be the default compiler used for Python on Windows, none of Roumen's
> patches change that. They would merely open up the choice for packagers and
> users to bu
r something
we should try to fix. For information on contributing to MSYS2 please
see https://sourceforge.net/p/msys2/wiki/Contributing%20to%20MSYS2/
Finally, this thread has contained many references to mingw, care
should be taken to be explicit about which of MinGW-w64 or mingw is
being referred
23 matches
Mail list logo
