Corey O'Brien coreypobr...@gmail.com added the comment:
Building py2exe with VS2010 I had this same issue and the /MANIFEST fix
mentioned here fixed the problem.
I also think that this issue should be re-opened.
--
nosy: +coreypobrien
___
Python
Sébastien Sablé sa...@users.sourceforge.net added the comment:
I got this problem again this morning while compiling pywin32.
This problem is not specific to me, anyone using Visual Studio 2010 to compile
Python is experiencing the same issue:
David Schnur dnsch...@gmail.com added the comment:
I haven't commented since opening this issue, but I've been following along.
Regarding Marc-Andre's latest comment, I think whether to embed a manifest or
not is a separate issue. The current behavior is to embed a manifest, and so
it
Sébastien Sablé sa...@users.sourceforge.net added the comment:
I encountered the same problem while compiling the psutil package.
I used Python 3.2.2 that I compiled myself using Visual Studio 2010 SP1 in
Debug mode by following the PCBuild/readme.txt documentation.
I could not compile psutil
Santoso Wijaya santoso.wij...@gmail.com added the comment:
And also with an extension module I'm trying to build with Python-2.7.1 AMD64.
Schnur's suggestion fixes it.
--
nosy: +santa4nt
___
Python tracker rep...@bugs.python.org
Santoso Wijaya santoso.wij...@gmail.com added the comment:
Another workaround is by adding the linker argument to Extension() as
extra_link_args:
extra_link_args=['/MANIFEST']
--
___
Python tracker rep...@bugs.python.org
Gregory Czajkowski gcflym...@gmail.com added the comment:
Also happening with python2.6 and building pyzmq-2.0.10 using easy_install.
dschnur's suggestion fixes it.
--
nosy: +gcflymoto
___
Python tracker rep...@bugs.python.org
David Joy videa...@gmail.com added the comment:
Hi Marc,
Well, I fried my original server install trying to trace this. My new fresh
install can still reproduce the problem with mysql-python, but I can't recreate
the issue with PyOpenSSL anymore. Grabbing packages at random from PyPi hasn't
David Joy videa...@gmail.com added the comment:
Hi All,
I just built mysql-python against CPython2.7 MSVC2008 Express Edition and
Server 2003 R2. All were freshly built on a clean Server 2003 install. This
exact issue occurred building with pip 0.8.1 on top of distribute 0.6.14:
C:\Program
Marc-Andre Lemburg m...@egenix.com added the comment:
Hi David,
since both you and Pavel are building mysql-python and using
setuptools (which applies a lot of hacks on stock distutils),
could you please also try some other package from PyPI in that
same configuration and preferably one which
Changes by Marc-Andre Lemburg m...@egenix.com:
Removed file: http://bugs.python.org/file13126/unnamed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue4431
___
Pavel Repin prepin+pythonb...@gmail.com added the comment:
I'd like to point out that on some configurations (at least mine), you
really need to specify /MANIFEST option to the linker, even though MSDN
documentation seems to imply that /MANIFEST behavior is ON by default.
My config:
beta
Marc-Andre Lemburg m...@egenix.com added the comment:
On 2009-02-17 20:22, Pavel Repin wrote:
Pavel Repin prepin+pythonb...@gmail.com added the comment:
I'd like to point out that on some configurations (at least mine), you
really need to specify /MANIFEST option to the linker, even though
Pavel Repin prepin+pythonb...@gmail.com added the comment:
Hi Marc,I am pretty sure it helped on my particular configuration.
I was trying to compile MySQL-python-1.2.2.tar.gz package from source and it
was failing in mt.exe step because the manifest file was not there.
I didn't do anything
Pavel Repin prepin+pythonb...@gmail.com added the comment:
Marc-Andre,
I can also repro this on Vista machine with the same Python MSVS
configuration.
This is the build error stemming from missing manifest file
(unnecessary details elided; note the absence of /MANIFEST option):
New submission from David Schnur [EMAIL PROTECTED]:
This is my first time submitting an issue; sorry if I am doing this
wrong. While attempting to build/install PyOpenSSL on Windows / MSVC,
the mt.exe step failed because it could not find the manifest file that
it was attempting to embed in
Amaury Forgeot d'Arc [EMAIL PROTECTED] added the comment:
Since issue4120, the compilation tools precisely chose to *not* embed
manifests in .pyd extensions.
This probably means that the mt.exe step should be skipped by
distutils.
--
assignee: - loewis
nosy: +amaury.forgeotdarc,
Marc-Andre Lemburg [EMAIL PROTECTED] added the comment:
On 2008-11-25 21:16, David Schnur wrote:
New submission from David Schnur [EMAIL PROTECTED]:
This is my first time submitting an issue; sorry if I am doing this
wrong. While attempting to build/install PyOpenSSL on Windows / MSVC,
Marc-Andre Lemburg [EMAIL PROTECTED] added the comment:
This is why we don't see the problem:
http://msdn.microsoft.com/en-us/library/f2c0w594.aspx
The default is /MANIFEST.
So it appears that you must have disabled this default somehow.
___
Python
David Schnur [EMAIL PROTECTED] added the comment:
I looked at this some more (I'm not super familiar with the use of
manifests) and I think I figured it out. For somewhat complicated
reasons, I'm compiling with /MT rather than /MD. Although link normally
produces a manifest, since it's
Martin v. Löwis [EMAIL PROTECTED] added the comment:
Closing it as invalid then.
--
resolution: - invalid
status: open - closed
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue4431
___
21 matches
Mail list logo
