Re: Python discussed in Nature

2015-02-15 Thread Chris Angelico
On Mon, Feb 16, 2015 at 8:09 AM, giacomo boffi 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 eve

Re: Python discussed in Nature

2015-02-15 Thread giacomo boffi
Chris Angelico writes: > On Sat, Feb 14, 2015 at 6:40 AM, John Ladasky > 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

Re: Python discussed in Nature

2015-02-13 Thread Sturla Molden
On 12/02/15 15:39, Marko Rauhamaa wrote: I write both Py2 and Py3 code, but I keep the two worlds hermetically separated from each other. In SciPy world we run the same code on Python 2 and Python 3. Sturla -- https://mail.python.org/mailman/listinfo/python-list

Re: Python discussed in Nature

2015-02-13 Thread Chris Angelico
On Sat, Feb 14, 2015 at 6:40 AM, John Ladasky 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

Re: Python discussed in Nature

2015-02-13 Thread John Ladasky
On Thursday, February 12, 2015 at 7:12:01 PM UTC-8, Steven D'Aprano wrote: > John Ladasky wrote: > > > 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 wi

Re: Python discussed in Nature

2015-02-12 Thread Terry Reedy
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.

Re: Python discussed in Nature

2015-02-12 Thread Rustom Mody
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

Re: Python discussed in Nature

2015-02-12 Thread Steven D'Aprano
John Ladasky wrote: > 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

Re: Python discussed in Nature

2015-02-12 Thread Steven D'Aprano
Marko Rauhamaa wrote: > Chris Angelico : > >> On Fri, Feb 13, 2015 at 1:39 AM, Marko Rauhamaa wrote: >>> I write both Py2 and Py3 code, but I keep the two worlds hermetically >>> separated from each other. >> >> [...] >> >> You don't need to be afraid of the gap. > > No problem. When I write Py

Re: Python discussed in Nature

2015-02-12 Thread Ethan Furman
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! -- ~Etha

Re: Python discussed in Nature

2015-02-12 Thread Chris Angelico
On Fri, Feb 13, 2015 at 5:29 AM, John Ladasky wrote: > 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

Re: Python discussed in Nature

2015-02-12 Thread John Ladasky
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

Re: Python discussed in Nature

2015-02-12 Thread Chris Angelico
On Fri, Feb 13, 2015 at 3:56 AM, Marko Rauhamaa wrote: > $ python3 > Python 3.4.1 (default, Nov 3 2014, 14:38:10) > [GCC 4.9.1 20140930 (Red Hat 4.9.1-11)] on linux > Type "help", "copyright", "credits" or "license" for more information. import sys sys.path = [ '/usr/lib64/python2.7' ]

Re: Python discussed in Nature

2015-02-12 Thread Marko Rauhamaa
Chris Angelico : > On Fri, Feb 13, 2015 at 1:39 AM, Marko Rauhamaa wrote: >> I write both Py2 and Py3 code, but I keep the two worlds hermetically >> separated from each other. > > [...] > > You don't need to be afraid of the gap. No problem. When I write Py3, I write Py3. When I write Py2, I wr

Re: Python discussed in Nature

2015-02-12 Thread Chris Angelico
On Fri, Feb 13, 2015 at 1:39 AM, Marko Rauhamaa wrote: > Fabien : > >> But this was exactly my point! Today in 2015 it's incredibly easy to >> write py2/py3 code for a scientist. The whole SciPy track has done the >> transition. Not an issue anymore either, for me at least (python >> youngster ;-)

Re: Python discussed in Nature

2015-02-12 Thread Marko Rauhamaa
Fabien : > But this was exactly my point! Today in 2015 it's incredibly easy to > write py2/py3 code for a scientist. The whole SciPy track has done the > transition. Not an issue anymore either, for me at least (python > youngster ;-) I write both Py2 and Py3 code, but I keep the two worlds herm

Re: Python discussed in Nature

2015-02-12 Thread Fabien
On 12.02.2015 12:25, Marko Rauhamaa wrote: Fabien: >... what a coincidence then that a huge majority of scientists >(including me) dont care AT ALL about unicode. You shouldn't, any more than you care about ASCII or 2's-complement encoding. Things should just work. And they do! Since almost

Re: Python discussed in Nature

2015-02-12 Thread Marko Rauhamaa
Fabien : > ... what a coincidence then that a huge majority of scientists > (including me) dont care AT ALL about unicode. You shouldn't, any more than you care about ASCII or 2's-complement encoding. Things should just work. > But since scientists are not paid to rewrite old code, the scientifi

Re: Python discussed in Nature

2015-02-12 Thread Fabien
On 12.02.2015 10:31, wxjmfa...@gmail.com wrote: [some OT stuffs about unicode] ... 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

Re: Python discussed in Nature

2015-02-12 Thread Mark Lawrence
On 12/02/2015 08:46, 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 Interesting. I'll leave someone more diplomatic than myself to repl

Python discussed in Nature

2015-02-12 Thread Steven D'Aprano
"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 -- Steve -- https://mail.python.org/mailman/listinfo/python-list