esolve for Python's
incredibly diverse user base.
Top-posted from my Windows Phone
-Original Message-
From: "Chris Angelico"
Sent: 5/26/2016 17:04
Cc: "python-dev"
Subject: Re: [Python-Dev] runtime dlls on Windows
On Fri, May 27, 2016 at 5:13 AM, Steve Dower wro
On Fri, May 27, 2016 at 5:13 AM, Steve Dower wrote:
> If they're installed properly into System32/SysWOW64 (using the official
> installer), then yes. If you simply drop them into your Python install
> directory, then no, unless you drop the right one - it has to match the
> python.exe architectur
On 26May2016 1601, Glenn Linderman wrote:
On 5/26/2016 3:18 PM, Steve Dower wrote:
This has been deprecated. It sounded like a great idea at the time (~8
years ago) but caused more problems than it solved.
Somehow I missed the announcement of the deprecation.
The feature itself probably hasn
On 5/26/2016 3:18 PM, Steve Dower wrote:
This has been deprecated. It sounded like a great idea at the time (~8
years ago) but caused more problems than it solved.
Somehow I missed the announcement of the deprecation.
When I first heard of Windows manifests, though, my first reaction was
that
On 26May2016 1453, Sebastian Krause wrote:
Chris Angelico wrote:
BUT -- Steve Dower seems to have identified that the wonders of dll hell
never cease, and this isn't possible anyway. Oh well.
I'm not entirely grasping what's happening here. There are multiple
versions of msvcp140.dll floating
Chris Angelico wrote:
>> BUT -- Steve Dower seems to have identified that the wonders of dll hell
>> never cease, and this isn't possible anyway. Oh well.
>
> I'm not entirely grasping what's happening here. There are multiple
> versions of msvcp140.dll floating around out there; what happens if
>
On 26/05/2016 19:02, Brett Cannon wrote:
On Thu, 26 May 2016 at 09:44 Chris Barker mailto:chris.bar...@noaa.gov>> wrote:
[SNIP]
Thanks Steve. Will you be at PyCon? if Nathaniel and I look at this
during the sprints, maybe you could coach us a bit.
Steve will be at PyCon but I don
On 26May2016 0942, Chris Barker wrote:
An alternative approach would be to stick MSVCP140.DLL into a tiny
shim wheel and upload that to PyPI, and then wxPython and matplotlib's
windows wheels could declare a dependency on this msvcp410 wheel.
Basically this is the idea of my pyna
On Thu, 26 May 2016 at 09:44 Chris Barker wrote:
> [SNIP]
> Thanks Steve. Will you be at PyCon? if Nathaniel and I look at this
> during the sprints, maybe you could coach us a bit.
>
Steve will be at PyCon but I don't think he will be around for the sprints
as he has to catch a flight out for
On Thu, May 26, 2016 at 9:53 AM, Chris Angelico wrote:
> > BUT -- Steve Dower seems to have identified that the wonders of dll hell
> > never cease, and this isn't possible anyway. Oh well.
>
> I'm not entirely grasping what's happening here.
me neither :-(
> There are multiple
> versions of
On Fri, May 27, 2016 at 2:42 AM, Chris Barker wrote:
> On Wed, May 25, 2016 at 1:40 PM, Chris Angelico wrote:
>>
>> But why should CPython
>> package a runtime that it doesn't use?
>
>
> Because it IS part of the "standard runtime environment" that cPython is
> providing. The cPython Windows buil
On Wed, May 25, 2016 at 1:40 PM, Chris Angelico wrote:
> But why should CPython
> package a runtime that it doesn't use?
Because it IS part of the "standard runtime environment" that cPython is
providing. The cPython Windows builds are built with a particular compiler
that expects a particular
On 25May2016 1229, Chris Barker wrote:
Hi folks,
The standard build of Py3.5 for Windows is built with VS2015 (correct??)
And it includes the runtime dlls it needs.
However, we've found that wxPython wheels for win32 (not sure about
win64) also need:
MSVCP140.DLL
There are two different vers
On Wed, May 25, 2016 at 12:29 PM, Chris Barker wrote:
>
> Hi folks,
>
> The standard build of Py3.5 for Windows is built with VS2015 (correct??) And
> it includes the runtime dlls it needs.
>
> However, we've found that wxPython wheels for win32 (not sure about win64)
> also need:
>
> MSVCP140.D
On 05/25/2016 04:37 PM, Ryan Gonzalez wrote:
Wouldn't downloading the Microsoft C++ Runtime 2015 also work? Many recent
computers already have it pre-installed.
Even though the download seems to be only 14 MB (I don't have a Windows
machine, so I cannot assure that just the file on MS website
On Thu, May 26, 2016 at 6:26 AM, Chris Barker wrote:
> the point here is that end users should be able to:
>
> pip install something
>
> and if there is a binary wheel for something, it should work without them
> having to install something else. (why MS doesn't ship ALL their runtimes
> with eh O
On Wed, May 25, 2016 at 12:37 PM, Ryan Gonzalez wrote:
> Wouldn't downloading the Microsoft C++ Runtime 2015 also work?
>
I'm sure it would -- I know that installing the entire MSVC2015 Community
Edition does...
but the point here is that end users should be able to:
pip install something
and
Wouldn't downloading the Microsoft C++ Runtime 2015 also work? Many recent
computers already have it pre-installed.
--
Ryan
[ERROR]: Your autotools build scripts are 200 lines longer than your
program. Something’s wrong.
http://kirbyfan64.github.io/
On May 25, 2016 2:31 PM, "Chris Barker" wrote:
Hi folks,
The standard build of Py3.5 for Windows is built with VS2015 (correct??)
And it includes the runtime dlls it needs.
However, we've found that wxPython wheels for win32 (not sure about win64)
also need:
MSVCP140.DLL
So: wxPython could include that of course, But it looks like it's gett
19 matches
Mail list logo
