On Thu, Nov 12, 2009 at 12:24 AM, Wolodja Wentland
wentl...@cl.uni-heidelberg.de wrote:
The FHS differentiates between various classes of files and defines
proper location for them. We could define platform dependent
standard infixes for the following data file classes for distribution
foo:
On Fri, Nov 13, 2009 at 6:22 AM, David Cournapeau
da...@ar.media.kyoto-u.ac.jp wrote:
Tarek Ziadé wrote:
A deprecation warning would be added in install, if it finds a local
option, rather
than a global. Meaning both would work in 2.7/3.2.
If changing the command line in incompatible ways
On Fri, Nov 13, 2009 at 18:22 +0900, David Cournapeau wrote:
On Thu, Nov 12, 2009 at 12:24 AM, Wolodja Wentland
wentl...@cl.uni-heidelberg.de wrote:
The FHS differentiates between various classes of files and defines
proper location for them. We could define platform dependent
standard
On Fri, Nov 13, 2009 at 1:18 PM, Floris Bruynooghe
floris.bruynoo...@gmail.com wrote:
[..]
Is that scraping, or just preparing finalized options using configure ?
Meaning other command would just have to get them when they run, if present ?
How would that work ? configure would create a file ?
On Fri, Nov 13, 2009 at 7:38 PM, Wolodja Wentland
wentl...@cl.uni-heidelberg.de wrote:
Could you elaborate on this idea please? Do you mean that megabars
plugins are shipped in a different distribution than megabar itself?
Yes. Imagine that I create a library, which includes a firefox plugin
On Fri, Nov 13, 2009 at 11:26:23AM +0100, Tarek Ziadé wrote:
On Fri, Nov 13, 2009 at 6:22 AM, David Cournapeau
da...@ar.media.kyoto-u.ac.jp wrote:
Tarek Ziadé wrote:
A deprecation warning would be added in install, if it finds a local
option, rather
than a global. Meaning both would work
On Fri, Nov 13, 2009 at 06:22:06PM +0900, David Cournapeau wrote:
On Thu, Nov 12, 2009 at 12:24 AM, Wolodja Wentland
wentl...@cl.uni-heidelberg.de wrote:
The FHS differentiates between various classes of files and defines
proper location for them. We could define platform dependent
On Fri, Nov 13, 2009 at 9:46 PM, Tarek Ziadé ziade.ta...@gmail.com wrote:
On Fri, Nov 13, 2009 at 1:18 PM, Floris Bruynooghe
floris.bruynoo...@gmail.com wrote:
[..]
Is that scraping, or just preparing finalized options using configure ?
Meaning other command would just have to get them when
On Fri, Nov 13, 2009 at 1:52 PM, David Cournapeau courn...@gmail.com wrote:
On Fri, Nov 13, 2009 at 9:46 PM, Tarek Ziadé ziade.ta...@gmail.com wrote:
On Fri, Nov 13, 2009 at 1:18 PM, Floris Bruynooghe
floris.bruynoo...@gmail.com wrote:
[..]
Is that scraping, or just preparing finalized
On Fri, Nov 13, 2009 at 21:36 +0900, David Cournapeau wrote:
On Fri, Nov 13, 2009 at 7:38 PM, Wolodja Wentland
wentl...@cl.uni-heidelberg.de wrote:
Could you elaborate on this idea please? Do you mean that megabars
plugins are shipped in a different distribution than megabar itself?
Yes.
On Fri, Nov 13, 2009 at 13:04 +, Floris Bruynooghe wrote:
+1
:-)
But don't expect all package maintainers to suddenly classify their
datafiles properly. Last time this got discussed there was
significant opposition to this, maintainers did not see the point and
didn't want *any* change
On Fri, Nov 13, 2009 at 21:36 +0900, David Cournapeau wrote:
Yes. Imagine that I create a library, which includes a firefox plugin
in python. I need to differentiate between what will end up in firefox
and the rest.
One thing I find noteworthy/horrifying about your *Firefox* plugin
example is
On Friday 13 November 2009 06:44:37 am Tarek Ziadé wrote:
Here's my proposal for this to happen, if you (and others) want to
contribute:
Let's build this new configure command in Distribute 0.7, together
with the APIs to read/write the data.
Then let's change the other commands
Tarek Ziadé wrote:
On Thu, Nov 12, 2009 at 12:31 PM, Jim Vickroy jim.vick...@noaa.gov wrote:
Hello,
Please excuse the repost (sent last week), but I'm hoping someone on the
list can get me on-track with a distutils problem.
I have just upgraded from Python 2.5 to 2.6.4 (MS Windows XP
On Fri, Nov 13, 2009 at 4:36 PM, Jim Vickroy jim.vick...@noaa.gov wrote:
[..]
Hello Tarek,
--install-scripts is not recognized (see below) -- at least with Python
2.6.4 on MS Windows.
In Python 2.5 *and* 2.6:
--install-scripts is an option for install
--install-script is an option for
On Nov 13, 2009, at 9:01 AM, Wolodja Wentland wrote:
This would mean that the *default* install should be PEP 370 compliant
or inside a virtualenv and that installing into system paths should be
enabled explicitly.
+1.
___
Distutils-SIG maillist
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Floris Bruynooghe wrote:
On Fri, Nov 13, 2009 at 06:22:06PM +0900, David Cournapeau wrote:
On Thu, Nov 12, 2009 at 12:24 AM, Wolodja Wentland
wentl...@cl.uni-heidelberg.de wrote:
The FHS differentiates between various classes of files and defines
What's the best way to delete the build directory both before and after
installation, using Distribute? I want to do it so the user will only need to
do
setup.py install, and the build directory will be pre- and post-deleted.
Thanks,
Ram.
___
ke, 2009-11-11 kello 21:42 +0100, Tarek Ziadé kirjoitti:
[clip]
Do you mean, an Extension that would require several compilers ?
I was thinking of a one-to-one relation between an Extension and a
compiler type, even if there are are multiple source files (in different
languages)
for this
I'm having trouble using Distribute's pkg_resources.require(). I posted a
question on StackOverflow:
http://stackoverflow.com/questions/1728676/pkgresources-require-doesnt-see-wxpython
I hope someone here has an answer.
Thanks, Ram.
___
Distutils-SIG
On Fri, 13 Nov 2009 15:25:38 -0500, Tres Seaver tsea...@palladion.com
wrote:
* configuration etc
* shared data usr/share/foo/
* readmeusr/share/foo/READMEREADME, TODO, ...
could
be automatically
Ram Rachum cool...@cool-rr.com writes:
What's the best way to delete the build directory both before and
after installation, using Distribute? I want to do it so the user will
only need to do setup.py install, and the build directory will be
pre- and post-deleted.
Does the ‘clean’ command do
Ben Finney ben+python at benfinney.id.au writes:
Ram Rachum cool-rr at cool-rr.com writes:
What's the best way to delete the build directory both before and
after installation, using Distribute? I want to do it so the user will
only need to do setup.py install, and the build directory
On Fri, Nov 13, 2009 at 10:04 PM, Floris Bruynooghe
floris.bruynoo...@gmail.com wrote:
On Fri, Nov 13, 2009 at 06:22:06PM +0900, David Cournapeau wrote:
On Thu, Nov 12, 2009 at 12:24 AM, Wolodja Wentland
wentl...@cl.uni-heidelberg.de wrote:
The FHS differentiates between various classes of
On Sat, Nov 14, 2009 at 8:28 AM, Ram Rachum cool...@cool-rr.com wrote:
Would I have to type it when calling setup.py?
I want something that won't require that, and
would work when the user does the normal setup.py
install.
You cannot delete the build directory automatically by default, that
New submission from Benjamin Riggs ri...@umn.edu:
line 191-2:
%install
python setup.py install --single-version-externally-managed
--root=$RPM_BUILD_ROOT --record-rpm=INSTALLED_OBJECTS
causes:
error: option --record-rpm not recognized
--
messages: 463
nosy: riggs
priority: bug
status:
On Sat, Nov 14, 2009 at 1:39 AM, David Cournapeau courn...@gmail.comwrote:
On Sat, Nov 14, 2009 at 8:28 AM, Ram Rachum cool...@cool-rr.com wrote:
Would I have to type it when calling setup.py?
I want something that won't require that, and
would work when the user does the normal setup.py
On Sat, Nov 14, 2009 at 8:43 AM, cool-RR cool...@cool-rr.com wrote:
What I really want is never having to worry about the build directory being
around after doing any actions with `setup.py`.
Then create a script to do so.
David
___
Distutils-SIG
On Sat, Nov 14, 2009 at 1:53 AM, David Cournapeau courn...@gmail.comwrote:
On Sat, Nov 14, 2009 at 8:43 AM, cool-RR cool...@cool-rr.com wrote:
What I really want is never having to worry about the build directory
being
around after doing any actions with `setup.py`.
Then create a script
cool-RR cool...@cool-rr.com writes:
What I really want is never having to worry about the build directory
being around after doing any actions with `setup.py`. Do you have any
other suggestion?
If you have determined that ‘setup.py install clean’ does what you want,
then you can create a
30 matches
Mail list logo
