On 11/26/06, tomer filiba [EMAIL PROTECTED] wrote:
i found several places in my code where i use positive infinity
(posinf) for various things, i.e.,
i like the concept, but i hate the 1e1 stuff... why not add
posint, neginf, and nan to the float type? i find it much more readable as:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Phillip J. Eby napsal(a):
Just a suggestion, but one issue that I think needs addressing is the FHS
language that leads some Linux distros to believe that they should change
Python's normal installation layout (sometimes in bizarre ways) (...)
At 02:38 PM 11/27/2006 +0100, Jan Matejek wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Phillip J. Eby napsal(a):
Just a suggestion, but one issue that I think needs addressing is the FHS
language that leads some Linux distros to believe that they should change
Python's normal
Way back on 11/22/06, Martin v. Löwis [EMAIL PROTECTED] wrote:
Nick Coghlan schrieb:
Martin v. Löwis wrote:
I personally consider it good style to rely on implementation details
of CPython;
Is there a 'do not' missing somewhere in there?
No - I really mean it. I can find nothing wrong
On Mon, Nov 27, 2006, Jason Orendorff wrote:
Way back on 11/22/06, Martin v. L?wis [EMAIL PROTECTED] wrote:
Nick Coghlan schrieb:
Martin v. L?wis wrote:
I personally consider it good style to rely on implementation details
of CPython;
Is there a 'do not' missing somewhere in there?
No -
On 11/27/06, Aahz [EMAIL PROTECTED] wrote:
On Mon, Nov 27, 2006, Jason Orendorff wrote:
Way back on 11/22/06, Martin v. L?wis [EMAIL PROTECTED] wrote:
[...] I can find nothing wrong with people relying on
reference counting to close files, for example. It's a property of
CPython, and not
Version 0.10 of the 'processing' package is available at the cheeseshop:
http://cheeseshop.python.org/processing
It is intended to make writing programs using processes almost the
same as writing
programs using threads. (By importing from 'processing.dummy' instead
of 'processing'
one can
Talin schrieb:
As far as rewriting it goes - I can only rewrite things that I understand.
So if you want this to change, you obviously need to understand the
entire distutils. It's possible to do that; some people have done
it (the understanding part) - just go ahead and start reading source
Phillip J. Eby schrieb:
Actually, I meant that (among other things) it should be clarified that
it's alright to e.g. put .pyc and data files inside Python library
directories, and NOT okay to split them up.
My gut feeling is that this is out of scope for the LSB. The LSB would
only specify
Jan Matejek schrieb:
+1 on that. There should be a clear (and clearly presented) idea of how
Python is supposed to be laid out in the distribution-provided /usr
hierarchy. And it would be nice if this idea complied to FHS.
The LSB refers to the FHS, so it is clear that LSB support for Python
On 11/27/06, Martin v. Löwis [EMAIL PROTECTED] wrote:
Talin schrieb:
As far as rewriting it goes - I can only rewrite things that I understand.
So if you want this to change, you obviously need to understand the
entire distutils. It's possible to do that; some people have done
it (the
Mike Orr wrote:
On 11/27/06, Martin v. Löwis [EMAIL PROTECTED] wrote:
Talin schrieb:
As far as rewriting it goes - I can only rewrite things that I understand.
So if you want this to change, you obviously need to understand the
entire distutils. It's possible to do that; some people have done
12 matches
Mail list logo
