[Ironpython-users] launcher cp#35064

[Pawel Jasinski]

I have a feeling, that by default when the only installed python is
ironpython launcher should use the 32 bit version.
Is it correct?
--pawel



On Wed, Jun 11, 2014 at 6:45 PM, Vernon D. Cole <vernondcole at gmail.com>
wrote:

> On Wed, Jun 11, 2014 at 5:06 PM, Jeff Hardy <jdhardy at gmail.com> wrote:
>
>> On Wed, Jun 11, 2014 at 3:46 PM, Vernon D. Cole <vernondcole at gmail.com>
>> wrote:
>>>
>>> On Tue, Jun 10, 2014 at 3:55 PM, Pawel Jasinski <
>>> pawel.jasinski at gmail.com> wrote:
>>>
>>>> On Tue, Jun 10, 2014 at 4:30 PM, Jeff Hardy <jdhardy at gmail.com> wrote:
>>>>
>>>>> On Tue, Jun 10, 2014 at 2:57 PM, Pawel Jasinski <
>>>>> pawel.jasinski at gmail.com> wrote:
>>>>>
>>>>>> I had to modify the C and I am not done yet. I made an author of
>>>>>> launcher Vinay Sajip and Marc Hammond aware of  our cp. The feedback is
>>>>>> very conservative:
>>>>>> https://bitbucket.org/vinay.sajip/pylauncher/issue/3/command-line-support-for-configuration
>>>>>> For now I will fork it so it doesn't delay 2.7.5
>>>>>>
>>>>>
>>>>> Does an unmodified launcher work with IronPython at all?
>>>>>
>>>>
>>>> yes, in a limited way described by Vernon.
>>>> 1. You have to either provide a full path to ipy as shebang
>>>> 2. Make sure ipy is in a path and use #! ipy as shebang
>>>>
>>>
>>> You can also have the full path to IronPython in a py.ini file, then use
>>> #!ipy as as shebang [assuming that you define "ipy" in your py.ini]. Then
>>> py.exe must be in the path, but IronPython does not have to be.  (That is
>>> the configuration that I use.)
>>>
>>
>> That's the existing launcher behaviour, right? Adding entries to an .ini
>> file with the installer is easy.
>>
>
> Correct!
> Quoting PEP-397:
>
>  Two .ini files will be searched by the launcher - ``py.ini`` in the
>     current user's "application data" directory (i.e. the directory returned
>     by calling the Windows function SHGetFolderPath with CSIDL_LOCAL_APPDATA,
>     %USERPROFILE%\AppData\Local on Vista+,
>     %USERPROFILE%\Local Settings\Application Data on XP)
>     and ``py.ini`` in the same directory as the launcher.
>
> Since the launcher is normally installed in C:\Windows, the usual location
> will be C:\Windows\py.ini
>
>
>>  First can be used if script is installed with setup and shebang is
>>>> modified at the time of installation
>>>>
>>>> Ideally, launcher should detect ipy installation based on registry
>>>> content - I have already something but not finished.
>>>> If shebang line is one of Unix virtual ones or missing, there is no way
>>>> to redirect launcher to use ipy as default.
>>>>
>>>> The existing launcher starts Python2 by default (even though it is
>>> installed with Python3).  If there is any installation of (C)Python2 in the
>>> registry, it will be launched, otherwise Python3.  I think that we need to
>>> follow that pattern, giving CPython2 the default position.  I have proposed
>>> adding a [default] section to py.ini so that a user can change that
>>> behavior on his own system.
>>>
>>
>> This is more interesting, since if IronPython is the only installed
>> Python then it should be used for scripts without #! lines.
>>
>
> I would agree.
>
> That could be done two ways:
> 1) by looking for IronPython in the registry (the same way the launcher
> finds CPython) but that would add a lot of code that the CPython
> maintainers might not like. (But, then again, they might, since it would
> eliminate the installation sequence problem below.)
>
> 2) it could be done by adding
>
>> [default]
>>
> ipy
>>
>  to the py.ini file (if that feature were to be supported).
>   The downside to that would be that if CPython were later installed on
> the same system, IronPython would continue to be preferred -- so the order
> of installation would change the behavior -- which is not a desirable thing.
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/ironpython-users/attachments/20140611/873f5a97/attachment.html>