I've been playing around with the bdist_rpm command in distutils and noticed that if a non pure module does not include a MANIFEST file then bdist_rpm fails because it doesn't include .h files (also sdist generates an unusable tar ball for the same module). Some of the comments in the distutils mention that without a manifest the sdist doesn't include the header files. Was this a policy decision or was it just because no one implemented something to get the header files?
Suchandra Thapa wrote:
I've been playing around with the bdist_rpm command in distutilsand noticed that if a non pure module does not include a MANIFEST file then bdist_rpm fails because it doesn't include .h files (also sdist generates an unusable tar ball for the same module). Some of the comments in the distutils mention that without a manifest the sdist doesn't include the header files. Was this a policy decision or was it just because no one implemented something to get the header files?
I guess this is by design: How should distutils which .h files to magically include in the MANIFEST ? The Extension() objects only have information about the used .c files and the directories where the headers live.
Hi,
Is it intended that users must escape their own strings, which are passed to the shell? As an example, if I wanted to define a string for the preprocessor, I would have to do something like this:
defines = [('VERSION',r'\"1.2.3\"')]
If I hadn't escaped the double quotes then the shell would have removed them*.
It took me a good five minutes to figure out this problem and I'm sure that others have hit this gotcha.
Cheers, Brian
* python -c "import sys; print `sys.argv`" test ['-c', 'test']
python -c "import sys; print `sys.argv`" "test" ['-c', 'test']
python -c "import sys; print `sys.argv`" ""test"" ['-c', 'test']
participants (3)
-
Brian Quinlan -
M.-A. Lemburg -
Suchandra Thapa