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

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

Python discussed in Nature

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

Contents

  Python discussed in Nature Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2015-02-12 19:46 +1100
    Re: Python discussed in Nature Mark Lawrence <breamoreboy@yahoo.co.uk> - 2015-02-12 09:19 +0000
    Re: Python discussed in Nature wxjmfauth@gmail.com - 2015-02-12 01:31 -0800
      Re: Python discussed in Nature Fabien <fabien.maussion@gmail.com> - 2015-02-12 12:07 +0100
        Re: Python discussed in Nature Marko Rauhamaa <marko@pacujo.net> - 2015-02-12 13:25 +0200
          Re: Python discussed in Nature Fabien <fabien.maussion@gmail.com> - 2015-02-12 12:33 +0100
            Re: Python discussed in Nature Marko Rauhamaa <marko@pacujo.net> - 2015-02-12 16:39 +0200
              Re: Python discussed in Nature Chris Angelico <rosuav@gmail.com> - 2015-02-13 02:59 +1100
                Re: Python discussed in Nature Marko Rauhamaa <marko@pacujo.net> - 2015-02-12 18:56 +0200
                  Re: Python discussed in Nature Chris Angelico <rosuav@gmail.com> - 2015-02-13 04:08 +1100
                  Re: Python discussed in Nature Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2015-02-13 14:07 +1100
              Re: Python discussed in Nature Sturla Molden <sturla.molden@gmail.com> - 2015-02-13 23:58 +0100
                Re: Python discussed in Nature wxjmfauth@gmail.com - 2015-02-14 00:39 -0800
        Re: Python discussed in Nature John Ladasky <john_ladasky@sbcglobal.net> - 2015-02-12 10:29 -0800
          Re: Python discussed in Nature Chris Angelico <rosuav@gmail.com> - 2015-02-13 05:37 +1100
            Re: Python discussed in Nature wxjmfauth@gmail.com - 2015-02-13 02:03 -0800
          Re: Python discussed in Nature Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2015-02-13 14:11 +1100
            Re: Python discussed in Nature wxjmfauth@gmail.com - 2015-02-12 23:05 -0800
            Re: Python discussed in Nature John Ladasky <john_ladasky@sbcglobal.net> - 2015-02-13 11:40 -0800
              Re: Python discussed in Nature Chris Angelico <rosuav@gmail.com> - 2015-02-14 09:45 +1100
                Re: Python discussed in Nature giacomo boffi <pecore@pascolo.net> - 2015-02-15 22:09 +0100
                  Re: Python discussed in Nature Chris Angelico <rosuav@gmail.com> - 2015-02-16 09:16 +1100
          Re: Python discussed in Nature Rustom Mody <rustompmody@gmail.com> - 2015-02-12 20:07 -0800
            Re: Python discussed in Nature Terry Reedy <tjreedy@udel.edu> - 2015-02-13 00:24 -0500
            Re: Python discussed in Nature wxjmfauth@gmail.com - 2015-02-12 23:02 -0800
              Re: Python discussed in Nature wxjmfauth@gmail.com - 2015-02-13 01:36 -0800
    Re: Python discussed in Nature Ethan Furman <ethan@stoneleaf.us> - 2015-02-12 10:48 -0800

Page 2 of 2 — ← Prev page 1 [2]

#85696

Chris Angelico <rosuav@gmail.com> writes:

> On Sat, Feb 14, 2015 at 6:40 AM, John Ladasky
> <john_ladasky@sbcglobal.net> wrote:
>> The default font that the Geany program editor uses on my Ubuntu
>> system renders everything I've tried.  When I look up that font in
>> Geany's Preferences menu, it is called, simply, "monospace".
>>
>
> That's a font alias. Unfortunately, I've never yet figured out a
> straight-forward way to snap the pointer;

when you know it, it's easy...

% fc-match mono
DejaVuSansMono.ttf: "DejaVu Sans Mono" "Book"
% 

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

#85697

On Mon, Feb 16, 2015 at 8:09 AM, giacomo boffi <pecore@pascolo.net> wrote:
>> That's a font alias. Unfortunately, I've never yet figured out a
>> straight-forward way to snap the pointer;
>
> when you know it, it's easy...
>
> % fc-match mono
> DejaVuSansMono.ttf: "DejaVu Sans Mono" "Book"
> %

Learn something new every day! Thanks Giacomo!

ChrisA

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

#85627

On Thursday, February 12, 2015 at 11:59:55 PM UTC+5:30, John Ladasky wrote:
> On Thursday, February 12, 2015 at 3:08:10 AM UTC-8, Fabien wrote:
> 
> > ... what a coincidence then that a huge majority of scientists 
> > (including me) dont care AT ALL about unicode. But since scientists are 
> > not paid to rewrite old code, the scientific world is still stuck to 
> > python 2.
> 
> I'm a scientist.  I'm a happy Python 3 user who migrated from Python 2 about two years ago.
> 
> And I use Unicode in my Python.  In implementing some mathematical models which have variables like delta, gamma, and theta, I decided that I didn't like the line lengths I was getting with such variable names.  I'm using δ, γ, and θ instead.  It works fine, at least on my Ubuntu Linux system (and what scientist doesn't use Linux?).  I also have special mathematical symbols, superscripted numbers, etc. in my program comments.  It's easier to read 2x³ + 3x² than 2*x**3 + 3*x**2.
> 
> I am teaching someone Python who is having a few problems with Unicode on his Windows 7 machine.  It would appear that Windows shipped with a less-than-complete Unicode font for its command shell.  But that's not Python's fault.

Haskell is a bit ahead of python in this respect:

Prelude> let (x₁ , x₂) = (1,2)
Prelude> (x₁ , x₂)
(1,2)

>>> (x₁ , x₂) = (1,2)
  File "<stdin>", line 1
    (x₁ , x₂) = (1,2)
      ^
SyntaxError: invalid character in identifier

But python is ahead in another (arguably more) important aspect:
Haskell gets confused by ligatures in identifiers; python gets them right

>>> flag = 1 
>>> flag
1

Prelude> let flag = 1 
Prelude> flag

<interactive>:4:1: Not in scope: `flag'

Hopefully python will widen its identifier-chars also

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

#85629

On 2/12/2015 11:07 PM, Rustom Mody wrote:
> On Thursday, February 12, 2015 at 11:59:55 PM UTC+5:30, John Ladasky wrote:
>> On Thursday, February 12, 2015 at 3:08:10 AM UTC-8, Fabien wrote:
>>
>>> ... what a coincidence then that a huge majority of scientists
>>> (including me) dont care AT ALL about unicode. But since scientists are
>>> not paid to rewrite old code, the scientific world is still stuck to
>>> python 2.
>>
>> I'm a scientist.  I'm a happy Python 3 user who migrated from Python 2 about two years ago.
>>
>> And I use Unicode in my Python.  In implementing some mathematical models which have variables like delta, gamma, and theta, I decided that I didn't like the line lengths I was getting with such variable names.  I'm using δ, γ, and θ instead.  It works fine, at least on my Ubuntu Linux system (and what scientist doesn't use Linux?).  I also have special mathematical symbols, superscripted numbers, etc. in my program comments.  It's easier to read 2x³ + 3x² than 2*x**3 + 3*x**2.
>>
>> I am teaching someone Python who is having a few problems with Unicode on his Windows 7 machine.  It would appear that Windows shipped with a less-than-complete Unicode font for its command shell.  But that's not Python's fault.
>
> Haskell is a bit ahead of python in this respect:
>
> Prelude> let (x₁ , x₂) = (1,2)
> Prelude> (x₁ , x₂)
> (1,2)
>
>>>> (x₁ , x₂) = (1,2)
>    File "<stdin>", line 1
>      (x₁ , x₂) = (1,2)
>        ^
> SyntaxError: invalid character in identifier
>
> But python is ahead in another (arguably more) important aspect:
> Haskell gets confused by ligatures in identifiers; python gets them right
>
>>>> flag = 1
>>>> flag
> 1
>
> Prelude> let flag = 1
> Prelude> flag
>
> <interactive>:4:1: Not in scope: `flag'
>
> Hopefully python will widen its identifier-chars also

Python (supposedly) follows the Unicode definition based on character 
classes, as documented.  If the Unicode definition in fact allows 
subscripts, then Python should also.  If you want Python to broaden its 
definition beyond unicode, you will have to advocate and persuade.  It 
will not 'just happen'.

-- 
Terry Jan Reedy

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

#85630

Le vendredi 13 février 2015 05:07:45 UTC+1, Rustom Mody a écrit :
> 
> Hopefully python will widen its identifier-chars also

On that side Python is doing correcty.
This has been already discussed.
See ???

It's time to spend some time in understanding
all this stuff, Unicode, Python, Python/Unicode
and the coding of characters.

I have the feeling most of you have a understanding
of Unicode only via Python.

Unicode is "independent" from computer languages or OS.
But all software has to use it.

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

#85635

Le vendredi 13 février 2015 08:03:05 UTC+1, wxjm...@gmail.com a écrit :
> Le vendredi 13 février 2015 05:07:45 UTC+1, Rustom Mody a écrit :
> > 
> > Hopefully python will widen its identifier-chars also
> 
> On that side Python is doing correcty.
> This has been already discussed.
> See ???
> 
> It's time to spend some time in understanding
> all this stuff, Unicode, Python, Python/Unicode
> and the coding of characters.
> 
> I have the feeling most of you have a understanding
> of Unicode only via Python.
> 
> Unicode is "independent" from computer languages or OS.
> But all software has to use it.

Having said this I'm the first to recognize there
plenty of things I'm not understanding.
Eg, I never compiled/built Python on Windows. I'm
not able to download/install the tools to do it.

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

#85604

[Multipart message — attachments visible in raw view] — view raw

On 02/12/2015 12:46 AM, Steven D'Aprano wrote:
>
> "Nature", one of the world's premier science journals, has published an 
> excellent article about programming in Python:
> 
> http://www.nature.com/news/programming-pick-up-python-1.16833

That is a very nice article, thanks for sharing!

--
~Ethan~

[toc] | [prev] | [standalone]

Page 2 of 2 — ← Prev page 1 [2]

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

csiph-web