Installer issue - cannot specify path for python

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Run PyBluez-0.15.win32-py2.5.exe
2. Installer complains, 'Python v2.5 req, which was not found in registry'
3. python bin cannot be specified 

What is the expected output? What do you see instead?
See attached

What version of the product are you using? On what operating system?
PyBluez-0.15.win32-py2.5. Win XP SP2

Please provide any additional information below.
Path for python cannot be pasted in to dialog box. Python v2.5 installed in 
C:\cygwin\bin

Original issue reported on code.google.com by dari...@gmail.com on 22 May 2008 at 5:12

Attachments:

• py_bin_notFound.PNG
• py_dir_notSelectable.PNG

[GoogleCodeExporter]

Can you please remove the hard-coded path you are using for python and allow 
the user to specify path in the 
installer? 

Original comment by dari...@gmail.com on 3 Jun 2008 at 2:53

[GoogleCodeExporter]

There is no hard-coded python path.  That's all done by the python distutils 
module
automatically, which searches the windows registry for Python installations.  
Since
Cygwin Python doesn't modify the windows registry, I don't think it will ever be
detected by any distutils module.  Do you know of other windows binary extension
modules for which this works?

Original comment by ashu...@gmail.com on 3 Jun 2008 at 5:37

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Ahh i see, yes cygwin will not add a windows registry key specifying the
python bin path.

So I suggest you add a feature in to the installer that will allow the
user to specify a path for python if one was not found in the
registry.

Can you do that please?

Thanks.

-Darin

Original comment by dari...@gmail.com on 3 Jun 2008 at 6:23

[GoogleCodeExporter]

It's unfortunately not as easy as you'd like.  The installer program is 
generated
automatically by python distutils, so I don't have much control over that 
process.

Original comment by ashu...@gmail.com on 3 Jun 2008 at 7:22

[GoogleCodeExporter]

Original comment by ashu...@gmail.com on 12 Jun 2008 at 4:31

• Changed state: WontFix

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

I correct my previous comment (deleted):
Error only occurs for 64bit Python installations - my mistake.

Original comment by mtd07...@fh-hagenberg.at on 17 Jun 2010 at 2:32