Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.python > #74566 > unrolled thread

Re: how to msi install Python to non-default target dir?

Started byChris Angelico <rosuav@gmail.com>
First post2014-07-17 02:09 +1000
Last post2014-07-17 02:27 +1000
Articles 3 — 2 participants

Back to article view | Back to comp.lang.python

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Re: how to msi install Python to non-default target dir? Chris Angelico <rosuav@gmail.com> - 2014-07-17 02:09 +1000
    Re: how to msi install Python to non-default target dir? Marko Rauhamaa <marko@pacujo.net> - 2014-07-16 19:22 +0300
      Re: how to msi install Python to non-default target dir? Chris Angelico <rosuav@gmail.com> - 2014-07-17 02:27 +1000

#74566 — Re: how to msi install Python to non-default target dir?

FromChris Angelico <rosuav@gmail.com>
Date2014-07-17 02:09 +1000
SubjectRe: how to msi install Python to non-default target dir?
Message-ID<mailman.11886.1405526990.18130.python-list@python.org>
On Wed, Jul 16, 2014 at 11:29 PM, Albert-Jan Roskam
<fomcl@yahoo.com.dmarc.invalid> wrote:
> It needs to be installed to the non-default location "c:\program files\python27".

Why must it? Are you aware that many programs have issues with spaces
in file names? That's one reason for Python's default installation
location NOT being in the stupidly-named Program Files. Putting Python
there may cause trouble with, for instance, binary extensions.

ChrisA

[toc] | [next] | [standalone]


#74568

FromMarko Rauhamaa <marko@pacujo.net>
Date2014-07-16 19:22 +0300
Message-ID<87wqbd2rzc.fsf@elektro.pacujo.net>
In reply to#74566
Chris Angelico <rosuav@gmail.com>:

> Why must it? Are you aware that many programs have issues with spaces
> in file names? That's one reason for Python's default installation
> location NOT being in the stupidly-named Program Files. Putting Python
> there may cause trouble with, for instance, binary extensions.

One of Python's advantages over, say, bash is that it can handle spaces
and other funny characters in pathnames.


Marko

[toc] | [prev] | [next] | [standalone]


#74569

FromChris Angelico <rosuav@gmail.com>
Date2014-07-17 02:27 +1000
Message-ID<mailman.11887.1405528043.18130.python-list@python.org>
In reply to#74568
On Thu, Jul 17, 2014 at 2:22 AM, Marko Rauhamaa <marko@pacujo.net> wrote:
> Chris Angelico <rosuav@gmail.com>:
>
>> Why must it? Are you aware that many programs have issues with spaces
>> in file names? That's one reason for Python's default installation
>> location NOT being in the stupidly-named Program Files. Putting Python
>> there may cause trouble with, for instance, binary extensions.
>
> One of Python's advantages over, say, bash is that it can handle spaces
> and other funny characters in pathnames.

Both Python and bash can handle spaces just fine. It's applications
that have trouble.

ChrisA

[toc] | [prev] | [standalone]


Back to top | Article view | comp.lang.python


csiph-web