On Sat, Nov 14, 2009 at 5:06 AM, Ben Finney ben+pyt...@benfinney.id.au wrote:
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
Tarek Ziadé kirjoitti:
On Sat, Nov 14, 2009 at 5:06 AM, Ben Finney ben+pyt...@benfinney.id.au wrote:
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
On Fri, Nov 13, 2009 at 9:55 PM, cool-RR cool...@cool-rr.com wrote:
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.
2009/11/14 Alex Grönholm alex.gronh...@nextday.fi:
[..]
Semi-related:
I was wondering if a pre/post install hook to the install command
could be useful.
Distribute itself uses something like that, doesn't it? Having standardized
pre/post-install hooks might be worth considering.
And that
Tarek Ziadé ziade.tarek at gmail.com writes:
On Fri, Nov 13, 2009 at 9:55 PM, cool-RR cool-rr at cool-rr.com wrote:
I'm having trouble using Distribute's pkg_resources.require(). I posted a
question on StackOverflow:
At 03:13 PM 11/11/2009 +0100, Tarek Ziadé wrote:
But you call it with install in your example, meaning that is is
called at install time, right ?
Or it is just that you want to get the --prefix value finalized and
computed by the install
command. If it's the later, I guess you will be able to
At 12:36 AM 11/12/2009 -0600, Robert Kern wrote:
Sorry, I edited out the bit at the last minute where I explained
that it would be great to have a centralized option-managing object
such that any command can ask what options were set on any other
regardless of the dependencies between
On Sat, Nov 14, 2009 at 2:46 PM, Ram Rachum cool...@cool-rr.com wrote:
[..]
I haven't investigated that egg-info thing, because it doesn't matter much to
me
what is the technical reason for this. The fact that `require` gave a false
positive, and not even under any special circumstances,
What is your Python version ? Starting at Python 2.5, all
distutils-based installers add an egg-info
file or folder alongside the packages it installs in your system.
If it's not present it could be a partial installation, or a bug. I
would be interested in your feedback
if you do
On Sat, Nov 14, 2009 at 7:10 PM, cool-RR cool...@cool-rr.com wrote:
[..]
I did it on 2.6, but then I tried also on 2.5 and 2.4, and it happened the
same. I looked in site-packages and didn't find a egg, but I don't know much
about eggs so I don't know.
we are looking for a file or a folder
import wxpython; wxpython
You will get the path of the package, and the egg-info is supposely
located alongside this package.
(It's actually `wx` when you use it, not `wxpython`).
I did that and got the path and searched around, but didn't find any egg.
Ram.
P.J. Eby p...@telecommunity.com writes:
The distutils is a definite case of superficial design flaws being so
annoying as to keep most people from noticing the fundamental design
flaws. ;-)
Douglas Adams, RIP.
--
\ “Nature hath given men one tongue but two ears, that we may |
`\
Hello
I've update PEP 345 with a first draft about the markers,
http://python.org/dev/peps/pep-0345/#environment-markers
PEP 390 is being reworked accordingly, but I guess we can have a new round of
comments on PEP 345 and PEP 386, as they can be accepted and added in Python
independently from
On Fri, Nov 13, 2009 at 3:46 PM, Jeremy Kloth jeremy.kl...@gmail.com wrote:
[..]
The exact thing being described has been done in 4Suite for 6 years (along
with many other distutils improvements). Feel free to take or discuss or
request help with any of the features/additions (like FHS layout
On Wed, Nov 11, 2009 at 11:49 PM, Pauli Virtanen p...@iki.fi wrote:
[..]
Just to throw some wild, perhaps obvious, and definitely unasked-for
ideas in the air (especially as I can't promise I can give any sustained
help here :/ ):
I suppose one option would be to factor *everything* related
On Saturday 14 November 2009 05:14:05 pm Tarek Ziadé wrote:
On Fri, Nov 13, 2009 at 3:46 PM, Jeremy Kloth jeremy.kl...@gmail.com
The way we've impl'd 'config' was as a prerequisite for 'build', just as
'build' is for 'install'. If any of the options stored by the 'config'
command are
On Nov 14, 2009, at 4:09 PM, Tarek Ziadé wrote:
Last, Requires-Python is introduced to define the version of Python.
I am not sure this is required anymore since Martin has added a Trove
classifier
for this. But in the meantime, this is stronger than a simple
classifier I think.
+1 for
Tarek Ziadé wrote:
And have the community create new ExtensionBuilder subclasses that
could be registered like command.
I don't see a need for registering anything. You should
just be able to explicitly say what tool to use for each
stage of the process.
I envisage something like this:
18 matches
Mail list logo
