Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.python > #70033 > unrolled thread

Language summit notes

Back to article view | Back to comp.lang.python

Contents

  Language summit notes Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2014-04-10 12:07 +0000
    Re: Language summit notes Ben Finney <ben+python@benfinney.id.au> - 2014-04-11 09:50 +1000
      Re: Language summit notes wxjmfauth@gmail.com - 2014-04-11 02:25 -0700
        Re: Language summit notes Mark Lawrence <breamoreboy@yahoo.co.uk> - 2014-04-11 13:48 +0100
          Re: Language summit notes Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2014-04-11 15:49 +0000
            Re: Language summit notes Mark Lawrence <breamoreboy@yahoo.co.uk> - 2014-04-11 16:57 +0100
            Re: Language summit notes Chris Angelico <rosuav@gmail.com> - 2014-04-12 02:02 +1000
              Re: Language summit notes Mark H Harris <harrismh777@gmail.com> - 2014-04-11 11:12 -0500
            Re: Language summit notes Mark Lawrence <breamoreboy@yahoo.co.uk> - 2014-04-11 17:16 +0100
              Re: Language summit notes wxjmfauth@gmail.com - 2014-04-12 05:25 -0700
                Re: Language summit notes Ned Batchelder <ned@nedbatchelder.com> - 2014-04-12 08:53 -0400
                  Re: Language summit notes wxjmfauth@gmail.com - 2014-04-13 00:38 -0700
                    Re: Language summit notes Terry Reedy <tjreedy@udel.edu> - 2014-04-13 16:13 -0400
                      Re: Language summit notes wxjmfauth@gmail.com - 2014-04-14 01:02 -0700
                      Re: Language summit notes wxjmfauth@gmail.com - 2014-04-14 01:03 -0700
                Re: Language summit notes Rustom Mody <rustompmody@gmail.com> - 2014-04-13 06:32 -0700

#70033 — Language summit notes

Today in Montreal Canada, there was a Language Summit to discuss the 
future of Python. Some highlights:

PyPy is only three bug fixes away from shipping support for Python 3.2!

Guido confirms that easing the transition from 2.x to 3.x code is a major 
priority. Version 2.7 is alive and in good health and not ready to be 
retired yet, but he's still against releasing a version 2.8.

Both IronPython and Jython hope to support Python 3 soon, Jython is being 
held back by a lack of contributors.

Packaging is hard. Very hard. There is a lot of work going on to try to 
improve packaging.

After five years experience in managing the transition between 2 and 3, 
the official recommendation is now the opposite of what it was five years 
ago: write a single code-base aimed at both 2 and 3, rather than trying 
to automate translation via 2to3 or other tools.

There is a lot of interest for optional type checking.

More in this email thread here:

https://mail.python.org/pipermail/python-dev/2014-April/133873.html



-- 
Steven D'Aprano
http://import-that.dreamwidth.org/

[toc] | [next] | [standalone]

#70074

Steven D'Aprano <steve+comp.lang.python@pearwood.info> writes:

> Today in Montreal Canada, there was a Language Summit to discuss the 
> future of Python. Some highlights: […]

> More in this email thread here:
> https://mail.python.org/pipermail/python-dev/2014-April/133873.html

Thanks very much for this! Core development is important to the whole
Python community, but time-consuming to keep abreast of. Summaries for
general consumption are very helpful.

-- 
 \     “I thought I'd begin by reading a poem by Shakespeare, but then |
  `\     I thought ‘Why should I? He never reads any of mine.’” —Spike |
_o__)                                                         Milligan |
Ben Finney

[toc] | [prev] | [next] | [standalone]

#70113

Unicode!

[toc] | [prev] | [next] | [standalone]

#70134

On 11/04/2014 10:25, wxjmfauth@gmail.com wrote:
>
> Unicode!
>

Works perfectly in Python 3.3+ thanks to the excellent work done as a 
result of http://legacy.python.org/dev/peps/pep-0393/, the Flexible 
String Representation, as we, with one noticable exception, are 
perfectly well aware of.

-- 
My fellow Pythonistas, ask not what our language can do for you, ask 
what you can do for our language.

Mark Lawrence

---
This email is free from viruses and malware because avast! Antivirus protection is active.
http://www.avast.com

[toc] | [prev] | [next] | [standalone]

#70148

On Fri, 11 Apr 2014 13:48:50 +0100, Mark Lawrence wrote:

> On 11/04/2014 10:25, wxjmfauth@gmail.com wrote:
>>
>> Unicode!
>>
>>
> Works perfectly in Python 3.3+ thanks to the excellent work done as a
> result of http://legacy.python.org/dev/peps/pep-0393/, the Flexible
> String Representation, as we, with one noticable exception, are
> perfectly well aware of.

Please don't bait JMF. Writing a post for the sole purpose of getting a 
reaction from others is the definition of trolling.



-- 
Steven D'Aprano
http://import-that.dreamwidth.org/

[toc] | [prev] | [next] | [standalone]

#70150

On 11/04/2014 16:49, Steven D'Aprano wrote:
> On Fri, 11 Apr 2014 13:48:50 +0100, Mark Lawrence wrote:
>
>> On 11/04/2014 10:25, wxjmfauth@gmail.com wrote:
>>>
>>> Unicode!
>>>
>>>
>> Works perfectly in Python 3.3+ thanks to the excellent work done as a
>> result of http://legacy.python.org/dev/peps/pep-0393/, the Flexible
>> String Representation, as we, with one noticable exception, are
>> perfectly well aware of.
>
> Please don't bait JMF. Writing a post for the sole purpose of getting a
> reaction from others is the definition of trolling.
>

If you wish to interpret my words as baiting that's fine by me.  From my 
perspective I'm simply making a statement of fact.

-- 
My fellow Pythonistas, ask not what our language can do for you, ask 
what you can do for our language.

Mark Lawrence

---
This email is free from viruses and malware because avast! Antivirus protection is active.
http://www.avast.com

[toc] | [prev] | [next] | [standalone]

#70152

On Sat, Apr 12, 2014 at 1:57 AM, Mark Lawrence <breamoreboy@yahoo.co.uk> wrote:
> If you wish to interpret my words as baiting that's fine by me.  From my
> perspective I'm simply making a statement of fact.

It's almost now debatable whether you were metabaiting Steven into
telling you off for trolling the resident troll...

The time when we could have sane threads started by a jmf post about
Unicode is now over. His posts no longer have false claims that crave
rebuttal, so I advise completely ignoring them, and him, until such
time as he makes a point worthy of a response.

ChrisA

[toc] | [prev] | [next] | [standalone]

#70154

On 4/11/14 11:02 AM, Chris Angelico wrote:

> It's almost now debatable whether you were metabaiting Steven into
> telling you off for trolling the resident troll...
>

QOTW

[toc] | [prev] | [next] | [standalone]

#70157

On 11/04/2014 17:02, Chris Angelico wrote:
> On Sat, Apr 12, 2014 at 1:57 AM, Mark Lawrence <breamoreboy@yahoo.co.uk> wrote:
>> If you wish to interpret my words as baiting that's fine by me.  From my
>> perspective I'm simply making a statement of fact.
>
> It's almost now debatable whether you were metabaiting Steven into
> telling you off for trolling the resident troll...
>
> The time when we could have sane threads started by a jmf post about
> Unicode is now over. His posts no longer have false claims that crave
> rebuttal, so I advise completely ignoring them, and him, until such
> time as he makes a point worthy of a response.
>
> ChrisA
>

I have no further comment to make, regardless of who says what.

-- 
My fellow Pythonistas, ask not what our language can do for you, ask 
what you can do for our language.

Mark Lawrence

---
This email is free from viruses and malware because avast! Antivirus protection is active.
http://www.avast.com

[toc] | [prev] | [next] | [standalone]

#70182

------

Regarding the Flexible String Representation, I have always
been very coherent in the examples I gave (usually with and/or
from an interactive intepreter - not relevant).
I never seen once somebody pointing or beeing able to point
what is wrong in those examples.

jmf

[toc] | [prev] | [next] | [standalone]

#70183

On 4/12/14 8:25 AM, wxjmfauth@gmail.com wrote:
> ------
>
> Regarding the Flexible String Representation, I have always
> been very coherent in the examples I gave (usually with and/or
> from an interactive intepreter - not relevant).
> I never seen once somebody pointing or beeing able to point
> what is wrong in those examples.

We aren't going to engage in this topic.  The previous discussions have 
always ended the same way. You should refer to those threads if you want 
to re-acquaint yourself with other people's views on your theory and 
discourse.

--Ned.

>
> jmf
>


-- 
Ned Batchelder, http://nedbatchelder.com

[toc] | [prev] | [next] | [standalone]

#70191

Le samedi 12 avril 2014 14:53:15 UTC+2, Ned Batchelder a écrit :
> On 4/12/14 8:25 AM, wxjmfauth@gmail.com wrote:
> 
> > ------
> 
> >
> 
> > Regarding the Flexible String Representation, I have always
> 
> > been very coherent in the examples I gave (usually with and/or
> 
> > from an interactive intepreter - not relevant).
> 
> > I never seen once somebody pointing or beeing able to point
> 
> > what is wrong in those examples.
> 
> 
> 
> We aren't going to engage in this topic.  The previous discussions have 
> 
> always ended the same way. You should refer to those threads if you want 
> 
> to re-acquaint yourself with other people's views on your theory and 
> 
> discourse.
> 
> 
> 
> --Ned.
> 
> 
> 
> >
> 
> > jmf
> 
> >
> 
> 
> 
> 

May I recall again, I mainly "pointed" facts, examples, ...
I can almost count on the fingers of one of my hands, the number
of users/posters, who tried to reproduce the examples I gave!
In fact, that's you (plural), who are dicussing (my examples).

jmf

[toc] | [prev] | [next] | [standalone]

#70198

Everyone, please ignore Jim's unicode/fsr trolling, which started in 
July 2012. Don't quote it, don't try to answer it.

-- 
Terry Jan Reedy

[toc] | [prev] | [next] | [standalone]

#70209

-----

Unicode <== Coding of the characters (all schemes) <== math.

For those who are interested in that field, I recommand to
try to understand why we (the world) have to live with
all these coding schemes.

jmf

[toc] | [prev] | [next] | [standalone]

#70210

Le dimanche 13 avril 2014 22:13:36 UTC+2, Terry Reedy a écrit :
> Everyone, please ignore Jim's unicode/fsr trolling, which started in 
> 
> July 2012. Don't quote it, don't try to answer it.
> 
> 
> 
> -- 
> 
> Terry Jan Reedy

-------

FYI:
I was waiting for the final 3.4 release.
I'm only now maintaining interactive interpreters
(with an "s") to toy with unicode (and the coding
of characters) and some other tasks.

Python succeeded to become some kind of an "anti
unicode" tool (in the math sense, "antisymmetric, non
symmetric, symmetric"). Very interesting.

jmf

[toc] | [prev] | [next] | [standalone]

#70196

On Saturday, April 12, 2014 5:55:22 PM UTC+5:30, wxjm...@gmail.com wrote:
> ------
> 
> Regarding the Flexible String Representation, I have always
> been very coherent in the examples I gave (usually with and/or
> from an interactive intepreter - not relevant).
> I never seen once somebody pointing or beeing able to point
> what is wrong in those examples.

Unicode: I am ignorant and interested. Clearly you know more than me (and 
perhaps many others here) and we could learn from you.

FSR and efficiency: I am barely interested. As is the case for most python users
[If efficiency is one's primary consideration one should not be using python]

Coherent: I dont know what that word means to you. To me it means acting in a 
way that eases and smoothens communication.
Now if one look at this post of yours and most others one finds:
- Poor or completely missing attribution
- Or large quotes with google-groups unfortunate double-line spacing

Does 'coherent' mean something different in French?
[This question may sound sarcastic but is at least part serious/genuine]

As for unicode I dont think Ive much more to say than Ive said here if you 
insist on remaining stuck on the FSR.

However do please adjust your posting style to become more acceptable/coherent
by reading https://wiki.python.org/moin/GoogleGroupsPython

[toc] | [prev] | [standalone]

Back to top | Article view | comp.lang.python

csiph-web