On Sat, Jun 27, 2009 at 4:04 PM, Gabor
Grothendieck wrote:
> I think that most python installations won't have a
> registry key set. I have python 2.6 and 2.5 on my
> machine but searching the registry found no
> occurrence of the string python. At least the path method
The Python 2.5 installer
I think that most python installations won't have a
registry key set. I have python 2.6 and 2.5 on my
machine but searching the registry found no
occurrence of the string python. At least the path method
has the advantage that if its not set then the user
only has to modify the path whereas if i
You can also try to find Python on Windows machines by
reading the registry using the R readRegistry function (added
sometime around R 2.7.0, I think). You can't count on the
information being there, but it often is, depending on how
Python was installed.
Using the registry seems to work better t
I actually have the same question, about ant. I assume this would be
what the SystemRequirements field in a package DESCRIPTION is for, but
at the moment it seems unused. Is there a plan about this ?
Romain
On 06/27/2009 05:44 PM, Carlos J. Gil Bellosta wrote:
Hello,
I have been unsuccessful
If you can assume its on your path then try this:
pth <- sapply(strsplit(Sys.getenv("PATH"), ";"), function(x)
file.path(x, "python.exe", fsep = "\\"))
pth[file.exists(pth)][1]
On Sat, Jun 27, 2009 at 11:44 AM, Carlos J. Gil
Bellosta wrote:
> Hello,
>
> I have been unsuccessfully struggling for a
Hello,
I have been unsuccessfully struggling for a programmatical method to
find out whether and where Python is installed.
The reason is that I am developing a package that depends on python.
On UNIX/UNIX-like systems I can quite safely assume that python is
directly callable via system if inst
