Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2002-June/025368.html below:

[Python-Dev] addressing distutils inability to track file dependencies

• Previous message: [Python-Dev] addressing distutils inability to track file dependencies
• Next message: [Python-Dev] addressing distutils inability to track file dependencies
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

> consider PIL, for example: in my source directory, I have the
> following files, checked out from a repository:
> 
>     setup.py
>     _imaging.c
>     *.c
>     PIL/*.py
> 
> I want to be able to run setup.py and end up with an _imaging.pyd
> in the same directory.  I don't want distutils to attempt to copy
> stuff from PIL/*.py to PIL/*.py, mess up other parts of my source
> tree, install any scripts (broken or not) in the Python directory, or
> just generally make an ass of itself when failing to copy readonly
> files on top of other readonly files.

I thought that the thing to do this was

  python setup.py build_ext -i

--Guido van Rossum (home page: http://www.python.org/~guido/)

• Previous message: [Python-Dev] addressing distutils inability to track file dependencies
• Next message: [Python-Dev] addressing distutils inability to track file dependencies
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4