Am 06.01.14 17:26, schrieb Michael Urman:
> Here's some more guesswork. Does it seem possible that msiexec is
> trying to verify the revocation status of the certificate used to sign
> the python .msi file? Per
> http://blogs.technet.com/b/pki/archive/2006/11/30/basic-crl-checking-with-certutil.asp
Am 08.01.14 16:03, schrieb Nick Coghlan:
> On 9 January 2014 00:43, Bob Hanson wrote:
>> When I read this comment of yours, Guido, I immediately started
>> wondering about this. You may well be right -- indeed, I have a
>> very old install (c.2007) which has not been updated (other than
>> one or
On 9 January 2014 00:43, Bob Hanson wrote:
> When I read this comment of yours, Guido, I immediately started
> wondering about this. You may well be right -- indeed, I have a
> very old install (c.2007) which has not been updated (other than
> one or three new MS "drivers").
>
> Perhaps the Python
[Top-post fixed (use-case is an exception to the GvR rule ;-) )
and some attributions restored with my additional comments
following for the ease of future readers.]
TL;DR: Outbound-connection attempts seem to be happening only to
me, therefore, most likely not a Python problem -- but some
problem
On Mon, Jan 6, 2014 at 9:43 AM, Guido van Rossum wrote:
> Since MSIEXEC.EXE is a legit binary (not coming from our packager) and
> Akamai is a legitimate company (MS most likely has an agreement with
> them), at this point I would assume that there's something that
> MSIEXEC.EXE wants to get from
On 6 January 2014 15:29, Bob Hanson wrote:
> At any rate, the attempts to connect to the network seem like
> undesirable behavior to this man. If pip is necessary, then some
> Window users may well end up without it -- and then not know why
> something later doesn't work.
I have installed python
Since MSIEXEC.EXE is a legit binary (not coming from our packager) and
Akamai is a legitimate company (MS most likely has an agreement with
them), at this point I would assume that there's something that
MSIEXEC.EXE wants to get from Akamai, which is unintentionally but
harmlessly triggered by the
[For the record: I'm running 32bit Windows XP (Pro) SP2 and
installing "for all users."]
TL;DR: No matter what I tried this morning re uninstalling and
reinstalling 3.4.0b2, pip or no pip, MSI still tried to connect
to the Akamai URLs.
On Sun, 05 Jan 2014 23:06:49 -0500, R. David Murray wrote:
>
Stephen J. Turnbull writes:
> .deploy.static.akamitechnologies.com (according to host ),
Ignore this; *my* aging eyes dropped the "A" in "akamAitechnologies.com".
Sorry for the noise.
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.py
On Sun, 5 Jan 2014 23:54:41 -0600, Tim Peters wrote:
[Bob Hanson]
> >> ... magnifying glass, I see it is two very long URLs ending with
> >> something like after the blah-blah: < ... akametechnology.com>
[Stephen J. Turnbull]
> > I suppose you tried cutting and pasting? [...]
Tried, but was uns
On 06.01.2014 05:12, Donald Stufft wrote:
ensurepip uses —no-index so it shouldn’t be hitting the network at all.
Do you have a test to ensure that ensurepip doesn't try to use network
connections? You could e.g. mock socket.create_connection() and
socket.socket() in a custom socket module. T
[Bob Hanson]
>> ... magnifying glass, I see it is two very long URLs ending with
>> something like after the blah-blah: < ... akametechnology.com>
[Stephen J. Turnbull]
> I suppose you tried cutting and pasting? Note that you don't need to
> be exact as long as you're pretty sure you got the whol
Bob Hanson writes:
> On Sun, 5 Jan 2014 20:09:23 -0600, Tim Peters wrote:
>
> > As Benjamin asked, could you please flesh out what
> > "blah-blah-blah-dot-com" means - what, exactly, was the site your
> > firewall warned you about?
>
> Forgive me, but I'm an old man with very poor vision.
ensurepip uses —no-index so it shouldn’t be hitting the network at all.
On Jan 5, 2014, at 11:06 PM, R. David Murray wrote:
> On Sun, 05 Jan 2014 19:32:15 -0800, Bob Hanson wrote:
>> On Sun, 5 Jan 2014 21:09:53 -0600, Tim Peters wrote:
>>> So it's just Akamai caching content. Common as mud. C
On Sun, 05 Jan 2014 19:32:15 -0800, Bob Hanson wrote:
> On Sun, 5 Jan 2014 21:09:53 -0600, Tim Peters wrote:
> > So it's just Akamai caching content. Common as mud. Can't say
> > specifically what was being cached, but it _could_ be that your ISP
> > contracts with Akamai.
>
> Still not followi
On Sun, 5 Jan 2014 21:09:53 -0600, Tim Peters wrote:
> [Bob Hanson]
> > Forgive me, but I'm an old man with very poor vision. Using my
> > magnifying glass, I see it is two very long URLs ending with
> > something like after the blah-blah: < ... akametechnology.com>
> >
> > More precisely, these t
[Bob Hanson]
> Forgive me, but I'm an old man with very poor vision. Using my
> magnifying glass, I see it is two very long URLs ending with
> something like after the blah-blah: < ... akametechnology.com>
>
> More precisely, these two IP addresses:
> 23.59.190.113:80
> 23.59.190.106:80
So
On Sun, 5 Jan 2014 20:09:23 -0600, Tim Peters wrote:
> As Benjamin asked, could you please flesh out what
> "blah-blah-blah-dot-com" means - what, exactly, was the site your
> firewall warned you about?
Forgive me, but I'm an old man with very poor vision. Using my
magnifying glass, I see it is
On 01/05/2014 06:02 PM, Bob Hanson wrote:
I'm presuming, still, that it is something to do with the "ensure
that pip is present on Windows" thing?
Perhaps you could help us out by telling us what site was trying to be accessed?
--
~Ethan~
___
Python
[Bob Hanson]
> ...
> Didn't think this likely, but I have now quintuple-checked
> everything again. Everything says I have the real McCoy
> msiexec.exe in its proper location -- just upgraded another app
> which used MSI installers and it went as per normal.
That sounds most likely to me too ;-)
[Bob Hanson]
> > This is the first time I ever installed a version of Python which
> > caused something called "MSIEXEC.EXE"
[Tim Peters]
> msiexec.exe is not part of the Python download.. msiexec.exe is part
> of the Windows operating system, and is precisely the program that
> installs .msi fil
[Benjamin Peterson]
> ...
> This is the first time I ever installed a version of Python which
> caused something called "MSIEXEC.EXE"
msiexec.exe is not part of the Python download.. msiexec.exe is part
of the Windows operating system, and is precisely the program that
installs .msi files (which
--
Regards,
Benjamin
On Sun, Jan 5, 2014, at 04:19 PM, Bob Hanson wrote:
> On Sun, 05 Jan 2014 13:20:50 -0800, Larry Hastings wrote:
>
> > On behalf of the Python development team, I'm pleased to announce
> > the second beta release of Python 3.4.
>
> Thanks, Larry and all the devs, your hard
On Sun, 05 Jan 2014 13:20:50 -0800, Larry Hastings wrote:
> On behalf of the Python development team, I'm pleased to announce
> the second beta release of Python 3.4.
Thanks, Larry and all the devs, your hard work is appreciated.
However, why does this new version look like adware or other
malwa
On behalf of the Python development team, I'm pleased to announce
the second beta release of Python 3.4.
This is a preview release, and its use is not recommended for
production settings.
Python 3.4 includes a range of improvements of the 3.x series, including
hundreds of small improvements and
25 matches
Mail list logo
