Message 74208 - Python tracker

➜

This issue tracker has been migrated to GitHub , and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author	jpe
Recipients	barry, christian.heimes, jpe, loewis, slee
Date	2008年10月02日.23:05:53
SpamBayes Score	0.025157126
Marked as misclassified	No
Message-id	<48E553C4.2030500@wingware.com>
In-reply-to	<48E54B7B.9080506@v.loewis.de>

Content
> I don't think this could even work: apparently, Vista disallows putting > a path into the name field. So extension modules will have to ship with > their own copy of the CRT (or link statically). I agree that this is the case. The closest thing I found to documentation of this is http://msdn.microsoft.com/en-us/library/ms235291.aspx under Deploying Visual C++ library DLLs as private assemblies. It specifies that the assembly be copied twice, once into the folder with the .exe and again into the folder with the .dll. I think the best option is to always install for everyone as administrator on Vista.

Content

> I don't think this could even work: apparently, Vista disallows putting
> a path into the name field. So extension modules will have to ship with
> their own copy of the CRT (or link statically).
I agree that this is the case. The closest thing I found to 
documentation of this is 
http://msdn.microsoft.com/en-us/library/ms235291.aspx under Deploying 
Visual C++ library DLLs as private assemblies. It specifies that the 
assembly be copied twice, once into the folder with the .exe and again 
into the folder with the .dll.
I think the best option is to always install for everyone as 
administrator on Vista.

History
Date	User	Action	Args
2008年10月02日 23:05:54	jpe	set	recipients: + jpe, loewis, barry, christian.heimes, slee
2008年10月02日 23:05:53	jpe	link	issue4018 messages
2008年10月02日 23:05:53	jpe	create

homepage