On 24 Sep 2014 15:15, Tim Golden m...@timgolden.me.uk wrote:
On 23/09/2014 18:05, Steve Dower wrote:
I'm also considering/experimenting with installing into Program
Files by default, but I suspect that isn't going to work out yet.
I'd like to see that go forward: I think it's increasingly
On 24 September 2014 06:13, Tim Golden m...@timgolden.me.uk wrote:
My only real misgiving here is that, for a few years, we'll need *three*
versions installed to build the active branches: 2008 for 2.7; 2010 for 3.4;
and 2014 for 3.5. Am I wrong?
Also, will 2014 express edition be able to
On 24.09.2014 03:48, Nick Coghlan wrote:
On 24 September 2014 03:05, Steve Dower steve.do...@microsoft.com wrote:
Larry Hastings wrote:
On 09/19/2014 03:31 PM, Barry Warsaw wrote:
I think we need a Python 3.5 Release Schedule PEP.
Just checked it in as PEP 478. It should show up here in a
On Wed, 24 Sep 2014 17:12:35 +1000
Nick Coghlan ncogh...@gmail.com wrote:
On 24 Sep 2014 15:15, Tim Golden m...@timgolden.me.uk wrote:
On 23/09/2014 18:05, Steve Dower wrote:
I'm also considering/experimenting with installing into Program
Files by default, but I suspect that isn't going
2014-09-23 2:22 GMT+02:00 Donald Stufft don...@stufft.io:
I think we need a Python 3.5 Release Schedule PEP.
Just checked it in as PEP 478. It should show up here in a few minutes:
http://legacy.python.org/dev/peps/pep-0478/
Comments?
It says 3.4.0 all through it.
It was too distrubing
On 09/24/2014 10:00 PM, Nick Coghlan ncogh...@gmail.com wrote:
Subject: Re: [Python-Dev] 3.5 release schedule PEP
On 24 Sep 2014 15:15, Tim Golden m...@timgolden.me.uk wrote:
On 23/09/2014 18:05, Steve Dower wrote:
I'm also considering/experimenting with installing into Program
Files by
On 24 September 2014 14:16, Mike Miller python-...@mgmiller.net wrote:
It has been a supported option for just shy of 15 years on 2.X... most if
not all the bugs (setuptools) were fixed a decade ago, and right now
thousands, if not millions of people are running it under Program Files
right
Most Windows setup are desktop configured with a single user. I would not
be shocked if pip installs modules only for the current user by default.
Maybe it could be an option in Python installer (pip system wide or user).
Victor
Le mercredi 24 septembre 2014, Paul Moore p.f.mo...@gmail.com a
On Wed, 24 Sep 2014 21:32:52 +0200
Victor Stinner victor.stin...@gmail.com wrote:
Most Windows setup are desktop configured with a single user. I would not
be shocked if pip installs modules only for the current user by default.
Maybe it could be an option in Python installer (pip system wide
Paul Moore wrote:
On 24 September 2014 14:16, Mike Miller python-...@mgmiller.net wrote:
It has been a supported option for just shy of 15 years on 2.X...
most if not all the bugs (setuptools) were fixed a decade ago, and
right now thousands, if not millions of people are running it under
On Sep 24, 2014, at 4:24 PM, Steve Dower steve.do...@microsoft.com wrote:
Paul Moore wrote:
On 24 September 2014 14:16, Mike Miller python-...@mgmiller.net wrote:
It has been a supported option for just shy of 15 years on 2.X...
most if not all the bugs (setuptools) were fixed a decade
Donald Stufft wrote:
One thing about *nix is even though you can’t write to your normal Python
install location without root, invoking pip with permissions (assuming you
have
them) is as easy as prefacing it with ``sudo`` in most cases. Does Windows
have
an equivalent or do you need to
Thanks for the insights, Steve.
More below...
On 24.09.2014 18:52, Steve Dower wrote:
M.-A. Lemburg wrote:
I'd rather be conservative here and wait for another Python release before
switching VC versions. There are a few important questions that need answers
before we can consider a new VC
Mike Miller wrote:
Paul Moore wrote:
One thing that I presume would be an issue. Isn't Program Files
protected in newer versions of Windows?
Yes, that's the feature that protects from malicious users/code editing
import
os to run format c:\, spam your address book, or look for credit
On 09/25/2014 08:50 AM, Steve Dower wrote:
Unfortunately not. The easy way is for the executable to declare that it
needs administrative privileges, and then the OS will take over and let you
approve/reject/sign-in/etc. according to your settings.
There is the runas command, though it could
Paul Moore wrote:
One thing that I presume would be an issue. Isn't Program Files protected in
newer versions of Windows?
Yes, that's the feature that protects from malicious users/code editing import
os to run format c:\, spam your address book, or look for credit card
numbers, etc.
It
On 09/25/2014 08:43 AM, Donald Stufft wrote:
One thing about *nix is even though you can’t write to your normal Python
install location without root, invoking pip with permissions (assuming you have
them) is as easy as prefacing it with ``sudo`` in most cases. Does Windows have
an equivalent
On 24 September 2014 22:29, Steve Dower steve.do...@microsoft.com wrote:
In my experience pip --user works just fine also. We use it on our unmanned
media players successfully.
This is good to know. Maybe we aren't as far away as we think.
Indeed. Moving towards having --user as the norm is
On Wed, 24 Sep 2014 22:56:20 +0100
Paul Moore p.f.mo...@gmail.com wrote:
On 24 September 2014 22:29, Steve Dower steve.do...@microsoft.com wrote:
In my experience pip --user works just fine also. We use it on our unmanned
media players successfully.
This is good to know. Maybe we aren't
M.-A. Lemburg wrote:
I'd rather be conservative here and wait for another Python release before
switching VC versions. There are a few important questions that need answers
before we can consider a new VC version:
* Will there be free versions available ?
* Will those free editions
On Tue, Sep 23, 2014 at 10:27 AM, Ned Deily n...@acm.org wrote:
Thanks for the feedback, Carol. Let us know via bugs.python.org of any
issues you see. BTW, the new installer format will be coming to Python
2.7.9 as well.
Are the supported platforms going to be the same? i.e.:
10.3+ --
On Thu, Sep 25, 2014 at 6:50 AM, Steve Dower steve.do...@microsoft.com wrote:
Donald Stufft wrote:
One thing about *nix is even though you can’t write to your normal Python
install location without root, invoking pip with permissions (assuming you
have
them) is as easy as prefacing it with
Yes, we enable the compile script.
As we require admin rights to install Python and system (not user) modules with
pip, the stdlib .pycs do get created under ProgramFiles at install time.
There might well be a situation where a system pipped module doesn't get
compiled, but to be honest the
On 9/24/2014 6:59 PM, Chris Angelico wrote:
That is, could pip
defer the declaration until it's parsed its command line args and
decided that it'll be installing into the system directory, but NOT
make that declaration if it's given --user, or if it's running inside
a venv, or anything else that
On 09/23/2014 06:48 PM, Nick Coghlan wrote:
On 24 September 2014 03:05, Steve Dower steve.do...@microsoft.com wrote:
I'd like to move the Windows versions onto the next release of VC (currently VC 14 until the branding
team figures out what to call it). There isn't a promised RTM date for VC
On 09/24/2014 08:04 AM, Victor Stinner wrote:
It was too distrubing to read 3.4 in the 3.5 schedule. I modified
the PEP directly, sorry Larry.
No sweat. I would have fixed it myself, but yesterday was a big travel day.
Thanks for fixing it!
//arry/
26 matches
Mail list logo
