On 18 Oct, 2012, at 19:29, Daniel Holth wrote:
> I'd like to submit the Wheel PEPs 425 (filename metadata), 426
> (Metadata 1.3), and 427 (wheel itself) for acceptance. The format has
> been stable since May and we are preparing a patch to support it in
> pip, but we need to earn consensus befor
(Oops, originally replied only to Mark)
Is a 3x3 array greater or less than a 2x4 array or another 3x3 array?
The contents of a 1D memory view may be sortable, but the "logical
structure" part isn't, and neither is any multi-dimensional view.
I'm surprised by the lack of inheritance support thou
On 18 Oct, 2012, at 19:29, Daniel Holth wrote:
> I'd like to submit the Wheel PEPs 425 (filename metadata), 426
> (Metadata 1.3), and 427 (wheel itself) for acceptance. The format has
> been stable since May and we are preparing a patch to support it in
> pip, but we need to earn consensus befor
On Wed, Oct 24, 2012 at 7:28 AM, Ronald Oussoren wrote:
>
> On 18 Oct, 2012, at 19:29, Daniel Holth wrote:
>
>> I'd like to submit the Wheel PEPs 425 (filename metadata), 426
>> (Metadata 1.3), and 427 (wheel itself) for acceptance. The format has
>> been stable since May and we are preparing a p
On Wed, Oct 24, 2012 at 7:04 AM, Ronald Oussoren wrote:
>
> On 18 Oct, 2012, at 19:29, Daniel Holth wrote:
>
>> I'd like to submit the Wheel PEPs 425 (filename metadata), 426
>> (Metadata 1.3), and 427 (wheel itself) for acceptance. The format has
>> been stable since May and we are preparing a p
On 10/23/2012 09:29 AM, Georg Brandl wrote:
Especially since you're suggesting a huge number of new files, I question the
argument of better navigability.
FWIW I'm -1 on it too. I don't see what the big deal is with "large"
source files. If you have difficulty finding your way around
unicod
I've received three messages in the past hour from mailman at
python.org notifying me of various attempts to receive a password
reminder or to remove me from python-dev. I hope they don't succeed.
--
--Guido van Rossum (python.org/~guido)
___
Python-Dev
On 10/24/2012 03:19 AM, Éric Araujo wrote:
Hello,
Le 12/10/2012 13:50, Petri Lehtinen a écrit :
It's two and a half weeks left, but I've not seen any announcements
yet!
Indeed, work and other commitments took over, so we (Montréal-Python)
decided to move the bug day instead of announcing it la
On Oct 25, 2012 2:06 AM, "Larry Hastings" wrote:
>
> On 10/23/2012 09:29 AM, Georg Brandl wrote:
>>
>> Especially since you're suggesting a huge number of new files, I
question the
>> argument of better navigability.
>
>
> FWIW I'm -1 on it too. I don't see what the big deal is with "large"
sourc
On Wed, Oct 24, 2012 at 9:19 PM, Guido van Rossum wrote:
> I've received three messages in the past hour from mailman at
> python.org notifying me of various attempts to receive a password
> reminder or to remove me from python-dev. I hope they don't succeed.
Are you asking us to CC you on all
On Oct 25, 2012, at 08:15 AM, Nick Coghlan wrote:
>OK, I need to weigh in after seeing this kind of reply. Large source files
>are discouraged in general because they're a code smell that points
>strongly towards a *lack of modularity* within a *complex piece of
>functionality*.
Modularity is goo
On Thu, Oct 25, 2012 at 8:37 AM, Barry Warsaw wrote:
> On Oct 25, 2012, at 08:15 AM, Nick Coghlan wrote:
>
>>OK, I need to weigh in after seeing this kind of reply. Large source files
>>are discouraged in general because they're a code smell that points
>>strongly towards a *lack of modularity* wi
Nick Coghlan writes:
> OK, I need to weigh in after seeing this kind of reply. Large source files
> are discouraged in general because they're a code smell that points
> strongly towards a *lack of modularity* within a *complex piece of
> functionality*.
Sure, but large numbers of tiny source
On Thu, Oct 25, 2012 at 2:22 PM, Stephen J. Turnbull wrote:
> Nick Coghlan writes:
>
> > OK, I need to weigh in after seeing this kind of reply. Large source files
> > are discouraged in general because they're a code smell that points
> > strongly towards a *lack of modularity* within a *compl
On 25.10.2012 08:42, Nick Coghlan wrote:
>> Why are any of these codecs here in unicodeobjectland in the first
>> place? Sure, they're needed so that Python can find its own stuff,
>> but in principle *any* codec could be needed. Is it just an heuristic
>> that the codecs needed for 99% of the wo
15 matches
Mail list logo
