Re: [Python-Dev] More optimisation ideas

2016-02-05 Thread Emile van Sebille

On 2/5/2016 10:38 AM, Brett Cannon wrote:



On Fri, 5 Feb 2016 at 10:34 Emile van Sebille mailto:em...@fenx.com>> wrote:



 >> Except for that nasty licensing issue requiring source code.
 >>
 >> Emile
 > Licensing requires, in the GPL at least, that the *modified*
sources be
 > made *available*, not that they be shipped with the product.
Looking at
 > the Python license, and what tools already do, there is zero need to
 > ship the source to stay compliant.

Hmm, the annotated Open Source Definition explicitly states "The program
must include source code" -- how did I misinterpret that?


Because you left off the part following: "... and must allow
distribution in source code as well as compiled form". This is entirely
a discussion of distribution in a compiled form.



Aah, 'must' is less restrictive in this context than I expected. When 
you combine the two halves the first part might be more accurately 
phrased as 'The program must make source code available' rather than 
'must include' which I understood to mean 'ship with'.


Emile


___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com


Re: [Python-Dev] More optimisation ideas

2016-02-05 Thread Emile van Sebille

On 2/5/2016 9:37 AM, Alexander Walters wrote:



On 2/5/2016 12:27, Emile van Sebille wrote:

On 2/1/2016 9:20 AM, Ethan Furman wrote:

On 02/01/2016 08:40 AM, R. David Murray wrote:



On the other hand, if the distros go the way Nick has (I think) been
advocating, and have a separate 'system python for system scripts' that
is independent of the one installed for user use, having the
system-only
python be frozen and sourceless would actually make sense on a
couple of
levels.


Agreed.


Except for that nasty licensing issue requiring source code.

Emile

Licensing requires, in the GPL at least, that the *modified* sources be
made *available*, not that they be shipped with the product. Looking at
the Python license, and what tools already do, there is zero need to
ship the source to stay compliant.


Hmm, the annotated Open Source Definition explicitly states "The program 
must include source code" -- how did I misinterpret that?


Emile

http://opensource.org/osd-annotated






___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com


Re: [Python-Dev] More optimisation ideas

2016-02-05 Thread Emile van Sebille

On 2/1/2016 9:20 AM, Ethan Furman wrote:

On 02/01/2016 08:40 AM, R. David Murray wrote:



On the other hand, if the distros go the way Nick has (I think) been
advocating, and have a separate 'system python for system scripts' that
is independent of the one installed for user use, having the system-only
python be frozen and sourceless would actually make sense on a couple of
levels.


Agreed.


Except for that nasty licensing issue requiring source code.

Emile



___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com


Re: [Python-Dev] Devguide: Add a table summarizing status of Python branches

2016-01-21 Thread Emile van Sebille

On 1/21/2016 10:42 AM, Paul Moore wrote:

On 21 January 2016 at 17:18, Brett Cannon  wrote:

It's live: https://docs.python.org/devguide/#status-of-python-branches


Nice :-)

Minor nit, the status column says "end of life", but the text below
the table uses the term "end of line" (as does the comment "Versions
older than 2.6 reached their end-of-line". From my experience, "end of
life" is the more common term.


I'd prefer end-of-support -- bet you can't count how many pre 2.5 
installations are still live.


Emile


___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com


Re: [Python-Dev] Third milestone of FAT Python

2015-12-06 Thread Emile van Sebille

On 12/4/2015 11:39 AM, MRAB wrote:

On 2015-12-04 19:22, Isaac Morland wrote:

On Fri, 4 Dec 2015, MRAB wrote:

> Constant folding is when, say, "1 + 2" replaced by "2".

Isn't that called backspacing?  ;-)


Oops! I meant "1 + 1", of course. Or "3". Either would work. :-)


Oh, you must surely have meant '1 and 2'

Looking-for-truth-in-all-the-wrong-places-ly y'rs,

Emile


___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com


[Python-Dev] A quick word on top posting

2015-07-20 Thread Emile van Sebille
Your +infinity could have easily been top posted -- particularly when 
there's no in-line comments that require context.


just-because-I'm-on-what-feels-like-a-300-baud-connection-ly yr's,

Emile


On 7/19/2015 2:16 PM, Mark Lawrence wrote:

On 19/07/2015 22:06, Brett Cannon wrote:





There is absolutely no reason we can't keep discussions cordial,
friendly, and on-point on this list and prevent this sort of debacle
from occurring again.



+infinity




___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com


Re: [Python-Dev] Python 4?

2014-04-03 Thread Emile van Sebille

On 4/3/2014 7:46 AM, Tres Seaver wrote:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 04/03/2014 10:36 AM, R. David Murray wrote:


More seriously, I don't believe there should ever be a Py4k the way
there was a Py3k, and would prefer not to feed any rumours that there
might be.


Amen!


+1

Can't we just refer to PySky and leave it at that?

:)

Emile



___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com


Re: [Python-Dev] Requesting pronouncement on PEP 463: Exception-catching expressions

2014-03-12 Thread Emile van Sebille

On 3/12/2014 1:44 PM, Chris Angelico wrote:


unless someone's going to employ me to champion PEPs full time :)
(Hmm. That would be an interesting job title on the resume.)


It's available now -- www.pepboys.com  :)

Emile

___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com


Re: [Python-Dev] Python 4: don't remove anything, don't break backward compatibility

2014-03-10 Thread Emile van Sebille

On 3/10/2014 12:29 PM, Chris Angelico wrote:


I don't think there'd be huge problems
with a 4.0 release that's just like 3.10 except that it's a little
more free with removal of deprecateds. Maybe that could be the point
at which 2.x compatibility is dropped,


... and the point at which those of us on 2.x jump over 3.x to 4.x.  :)

Emile



___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com


Re: [Python-Dev] PEP 460: allowing %d and %f and mojibake

2014-01-13 Thread Emile van Sebille

On 1/13/2014 4:06 PM, Greg Ewing wrote:



of text methods -- together with a text-like literal
syntax and default repr(), even though at least half
the time they're completely inappropriate!


Better said as 'half the time they're coincidentally helpful!'

My $.01  :)

Emile



___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com


Re: [Python-Dev] PEP 460: allowing %d and %f and mojibake

2014-01-12 Thread Emile van Sebille

On 01/12/2014 11:30 AM, Emile van Sebille wrote:

On 01/12/2014 09:26 AM, Paul Moore wrote:

Can you give an example of code that is *nearly* acceptable to you,
which works in Python 2 and 3 today, and explain what improvements you
would like to see to it in order to use it instead of waiting for a
core change?



I'm not a developer, but I'm trying to understand how in v3 I accomplish
what in v2 is easy:

len(open('chars','wb').write("".join(map (chr,range(256.read())


my bad :

>>> open('chars','wb').write("".join(map (chr,range(256
>>> len(open('chars','rb').read())
256




What's the v3 equivalent?

Emile






___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com


Re: [Python-Dev] PEP 460: allowing %d and %f and mojibake

2014-01-12 Thread Emile van Sebille

On 01/12/2014 09:26 AM, Paul Moore wrote:

Can you give an example of code that is *nearly* acceptable to you,
which works in Python 2 and 3 today, and explain what improvements you
would like to see to it in order to use it instead of waiting for a
core change?



I'm not a developer, but I'm trying to understand how in v3 I accomplish 
what in v2 is easy:


len(open('chars','wb').write("".join(map (chr,range(256.read())

What's the v3 equivalent?

Emile



___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com


Re: [Python-Dev] General Q&A regarding Python 3, adoption etc.

2014-01-06 Thread Emile van Sebille

On 1/6/2014 3:16 PM, Nick Coghlan wrote:


I thought I mentioned it on this list last year when I first wrote it,
but some messages I've seen recently suggest many folks haven't seen it
before.


And even more will see it if you provide a link.

Please.

Emile


___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com