RE: Beginner in python

. Avi -Original Message- From: Python-list On Behalf Of Chris Angelico Sent: Monday, October 25, 2021 6:25 PM To: Python Subject: Re: Beginner in python On Tue, Oct 26, 2021 at 9:23 AM Kian Kwame wrote: > > hi buddie > am new to python somebody kindly advice the coding which w

Re: Beginner in python

On Tue, Oct 26, 2021 at 9:23 AM Kian Kwame wrote: > > hi buddie > am new to python somebody kindly advice the coding which will count odd > number from 1 to 10 , and counting number from 1 tp 100 Sounds like homework. What have you written so far? ChrisA --

Beginner in python

hi buddie am new to python somebody kindly advice the coding which will count odd number from 1 to 10 , and counting number from 1 tp 100 -- https://mail.python.org/mailman/listinfo/python-list

Re: Beginner problem, please help. Building a simple menu + lists , cannot print list

On Tue, Oct 12, 2021 at 9:13 AM Felix Kjellström wrote: > > Hello! Please see the link to the code I have uploaded to my account at > replit.com > > https://replit.com/join/lftxpszwrv-felixkjellstrom Unfortunately, it's not public. Are you able to put the code on GitHub as a repository or gist,

Beginner problem, please help. Building a simple menu + lists , cannot print list

Hello! Please see the link to the code I have uploaded to my account at replit.com https://replit.com/join/lftxpszwrv-felixkjellstrom Problem: When you select the menu option "Add buyer", you can enter three values. See code line 5, "def Add_buyer ():" Then, you use the arrow keys to select

[issue43614] Search is not beginner friendly

Ammar Askar added the comment: Just a little update to this, now that issue34398 is fixed it is possible to make this more beginner friendly by making sure the right terms have glossary entries. As an example, here is a search for "argument" on the latest docs: https://docs.pytho

[issue43614] Search is not beginner friendly

Anthony Flury added the comment: Is PR 25045 the correct Pull request - this Issue is a documentation change - the linked PR is related to Issue 43433 (a change to xmlrpc.client ?) -- ___ Python tracker

[issue43614] Search is not beginner friendly

Change by Chris Angelico : -- keywords: +patch nosy: +Rosuav nosy_count: 5.0 -> 6.0 pull_requests: +23797 stage: -> patch review pull_request: https://github.com/python/cpython/pull/25045 ___ Python tracker

[issue43614] Search is not beginner friendly

Change by Kamil Turek : -- nosy: +kamilturek ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue43614] Search is not beginner friendly

Serhiy Storchaka added the comment: Ha! I just was going to open the same issue (perhaps we read the same post on Quora). I concur that it is perhaps worth to add index entries for common parameter names (args, kwargs, self, cls) and also for *args and **kwargs and add notions that such

[issue43614] Search is not beginner friendly

. It is my view that the documentation should be beginner friendly, but in this case (and many other I guess) you have to know what to search for to find something useful. I note that even common phrases in Computing (such as 'variable arguments' or 'variable parameters') don't find anything useful

Re: (Issue resolved!) Issue with Python module downloads from Library for a beginner Python coder.

Hi terry, I am so happy to mention that your suggestion worked! I moved the file from Tkinter to Lib and I am suddenly able to import the file.  Thanks you so much @Bob, @Arjun, @Cameron for your suggestions. I can finally move forward. I hope to contribute to this community in future after

Re: Issue with Python module downloads from Library for a beginner Python coder.

Hello Dennis, Sorry for my copy-paste error and thanks for highlighting the same. I will make sure that from next time I will maintain the line breaks. I tried opening it in CMD and it did open with the skewed triangle figure although I am still not able to use it in my IDLE environment.

Re: Issue with Python module downloads from Library for a beginner Python coder.

On 8/2/2020 2:36 AM, Sarvesh Poddar via Python-list wrote: [I downloaded] https://mcsp.wartburg.edu/zelle/python/graphics.py) I have unmangled the traceback and added explanations. Traceback (most recent call last):  File "", line 1, in     import graphics You typed this in IDLE Shell in

Re: Issue with Python module downloads from Library for a beginner Python coder.

Do you have tkinter installed? The graphics.py module needs it to run. On Sat, Aug 1, 2020 at 11:36 PM Sarvesh Poddar via Python-list < python-list@python.org> wrote: > Hi, > I am currently using Python 3.8.5 with IDLE environment that comes > pre-installed with the Python application. I am

Re: Issue with Python module downloads from Library for a beginner Python coder.

Diverting replies to tu...@python.org, a better place for all this. It looks like the error is in graphics.py, not in your file. Your line: from graphics import * is syntacticly correct. Something has mangled the line breaks in your traceback, which here appears as: When I write a

Re: Issue with Python module downloads from Library for a beginner Python coder.

Hi, I am currently using Python 3.8.5 with IDLE environment that comes pre-installed with the Python application. I am using the book "An Introduction to computer science" by John Zelle as my reference. The problem I am facing is "There is a python program named "graphics.py" that is used as

Re: Issue with Python installation for a beginner Python coder.

On Thu, Jul 30, 2020 at 9:24 AM Sarvesh Poddar via Python-list wrote: > I re-installed Python in my Windows system as the earlier one was not able to > import modules... You do not provide much detail to diagnose what your problem(s) is(are). By the "earlier one" is it the same version as the

Issue with Python installation for a beginner Python coder.

Hi, I re-installed Python in my Windows system as the earlier one was not able to import modules. But now I am not able to open IDLE after multiple tries.  Can you guys help me? I am a beginner and tried out a lot of solutions provided on the internet and it's just not getting fixed. Please help

[issue21625] Make help() beginner helpful when no PAGER or LESS variable

Nagarajan added the comment: I would request us to think about a couple more options while this is under consideration... Do we want to also add the flags -X and -F to the less options? The -X flag gets less to show its output inline, instead of a separate screen. The advantage here is

[issue21625] Make help() beginner helpful when no PAGER or LESS variable

Change by Zackery Spytz : -- keywords: +patch nosy: +ZackerySpytz nosy_count: 7.0 -> 8.0 pull_requests: +20657 stage: needs patch -> patch review pull_request: https://github.com/python/cpython/pull/21520 ___ Python tracker

Re: [Beginner] Spliting input

Hi, On 25/06/2020 12:50, Bischoop wrote: I try to split input numbers, for example: 12 so I cant add them, I tried separated split(' ') but it's not working. Any ideas how to do this? * numb1,numb2=input("enter 1st and 2nd no ").split() Avg=(int(numb1) + int(numb2)) / 2 print(Avg) So, this

Re: [Beginner] Spliting input

Bischoop wrote: > I try to split input numbers, for example: 12 so I cant add them, I > tried separated split(' ') but it's not working. > Any ideas how to do this? > > * > numb1,numb2=input("enter 1st and 2nd no ").split() > Avg=(int(numb1) + int(numb2)) / 2 > print(Avg) > * > > -- > Thanks

Re: [Beginner] Spliting input

On 2020-06-25 2:13 PM, Bischoop wrote: On 2020-06-25, Andrew Bell wrote: Without knowing the problem you're having, it's hard to answer. This seems generally correct. Error track: Traceback (most recent call last): File "splitting.py", line 1, in numb1,numb2=input("enter 1st and

Re: [Beginner] Spliting input

On 2020-06-25, Andrew Bell wrote: > Without knowing the problem you're having, it's hard to answer. > This seems generally correct. > > Error track: Traceback (most recent call last): File "splitting.py", line 1, in numb1,numb2=input("enter 1st and 2nd no ").split() ValueError: not

Re: [Beginner] Spliting input

Without knowing the problem you're having, it's hard to answer. This seems generally correct. On Thu, Jun 25, 2020 at 7:57 AM Bischoop wrote: > I try to split input numbers, for example: 12 so I cant add them, I > tried separated split(' ') but it's not working. > Any ideas how to do this? > >

[Beginner] Spliting input

I try to split input numbers, for example: 12 so I cant add them, I tried separated split(' ') but it's not working. Any ideas how to do this? * numb1,numb2=input("enter 1st and 2nd no ").split() Avg=(int(numb1) + int(numb2)) / 2 print(Avg) * -- Thanks --

Re: beginner question-very basic

On Sun, 11 Aug 2019 12:50:29 -0400, slefkowitz wrote: > Just getting started with Python. > > Downloaded 3.7.4 rom python.org > > I wrote program in Notepad, saved it with a ".py" extension. > > What do I do next? How do I execute a program? I am assuming you are using Windows since you

beginner question-very basic

Just getting started with Python. Downloaded 3.7.4 rom python.org I wrote program in Notepad, saved it with a ".py" extension. What do I do next? How do I execute a program? -- https://mail.python.org/mailman/listinfo/python-list

[issue21625] Make help() beginner helpful when no PAGER or LESS variable

Terry J. Reedy added the comment: I recently opened Python in a Mac Terminal (bash) window, tried help(ob), and being a beginner in this situation, had the same terrible frustrating experience. I am leaving this open to implement David Murray's suggestion and changed the title accordingly

Re: Good virtualenv and packaging tutorials for beginner?

Leam Hall writes: > Folks on IRC have suggested using virtualenv to test code under > different python versions. Sadly, I've not found a virtualenv tutorial > I understand. Anyone have a link to a good one? I recently used

Re: Good virtualenv and packaging tutorials for beginner?

On Oct 4, 2017, at 3:49 AM, Leam Hall wrote: > > Folks on IRC have suggested using virtualenv to test code under different > python versions. Sadly, I've not found a virtualenv tutorial I understand. > Anyone have a link to a good one? > > The next step will be to figure

Re: Good virtualenv and packaging tutorials for beginner?

On 4 October 2017 at 13:30, leam hall wrote: > On Wed, Oct 4, 2017 at 7:15 AM, Ben Finney > wrote: > >> Leam Hall writes: >> >> > Folks on IRC have suggested using virtualenv to test code under >> > different python versions.

Re: Good virtualenv and packaging tutorials for beginner?

On Wed, Oct 4, 2017 at 7:15 AM, Ben Finney wrote: > Leam Hall writes: > > > Folks on IRC have suggested using virtualenv to test code under > > different python versions. Sadly, I've not found a virtualenv tutorial > > I understand. Anyone have a

Re: Good virtualenv and packaging tutorials for beginner?

Leam Hall writes: > Folks on IRC have suggested using virtualenv to test code under > different python versions. Sadly, I've not found a virtualenv tutorial > I understand. Anyone have a link to a good one? The Python Packaging Authority has a guide

Good virtualenv and packaging tutorials for beginner?

Folks on IRC have suggested using virtualenv to test code under different python versions. Sadly, I've not found a virtualenv tutorial I understand. Anyone have a link to a good one? The next step will be to figure out how to package a project; a good tutorial URL would be appreciated on

Re: TIC TAE TOE's problem(i am beginner)

> > P=input("X/O:") > if P=="X": > my_func1() > else: > my_func2() > > > > why cant function to print X or O win... > As a beginner I'd try to code using Python idioms rather than writing Python using BASIC

TIC TAE TOE's problem(i am beginner)

A=['1', ' ', '1'] B=['1', ' ', '2'] C=['1', ' ', '3'] D=['2', ' ', '1'] E=['2', ' ', '2'] F=['2', ' ', '3'] G=['3', ' ', '1'] H=['3', ' ', '2'] I=['3', ' ', '3'] N=int(9) def my_func1(): X=list(input()) global N N=N-1 if X==['1', ' ', '1']: A="X" my_func3()

Re: Beginner help

On Sunday, February 5, 2017 at 11:27:19 PM UTC, pha...@u.rochester.edu wrote: > Hi everyone. I'm new to python and have hit a bit of a wall with an > assignment I'm working on. I created a number of classes and instantiated > them, now I need to create a list out of them. I am looking for

Beginner help

Hi everyone. I'm new to python and have hit a bit of a wall with an assignment I'm working on. I created a number of classes and instantiated them, now I need to create a list out of them. I am looking for something more elegant than appending each object to the list as I instantiate it. I

Re: Is 'learning python 5th edition' a good book to beginner?

On Sun, Sep 25, 2016 at 3:50 PM, Lawrence D’Oliveiro wrote: > Judging from the table of contents > , it spends too much time > (i.e. > 0) talking about Python 2. I own this book. The 5th edition covers both Python 3.3

Re: Is 'learning python 5th edition' a good book to beginner?

Judging from the table of contents , it spends too much time (i.e. > 0) talking about Python 2. -- https://mail.python.org/mailman/listinfo/python-list

Is 'learning python 5th edition' a good book to beginner?

I want to find a python book like C++ primer which provides me details to understand the language. -- https://mail.python.org/mailman/listinfo/python-list

Re: DLL Error from a beginner

On 13-9-2016 23:59, srfp...@gmail.com wrote: > Running Pyscripter and Python version 2.7.12 on Win10 Home on a 64bit Laptop > 1. A simple Python application runs successfully. > 2. WxPython(wxPython3.0-win64-3.0.2.0-py27(1).exe executed successfully > 3. To the simple app above, I add import

DLL Error from a beginner

Running Pyscripter and Python version 2.7.12 on Win10 Home on a 64bit Laptop 1. A simple Python application runs successfully. 2. WxPython(wxPython3.0-win64-3.0.2.0-py27(1).exe executed successfully 3. To the simple app above, I add import wx and an Error Dialog occurs: ImportError:

Re: Beginner Question

gt;> > >> On Wed, Jun 1, 2016 at 9:42 PM, boB Stepp <robertvst...@gmail.com> wrote: > >>> On Wed, Jun 1, 2016 at 7:55 PM, Marcin Rak <m...@sightlineinnovation.com> > >>> wrote: > >>>> Hi to all > >>>> > >>>>

Re: Beginner Question

t; On Wed, Jun 1, 2016 at 7:55 PM, Marcin Rak <m...@sightlineinnovation.com> >>> wrote: >>>> Hi to all >>>> >>>> I have a beginner question to which I have not found an answer I was able >>>> to understand. Could someone explain why

Re: Beginner Question

That linked help clear up my confusion...yes you really have to know how things work internally to understand why things happen the way they happen. Thanks again to all -- https://mail.python.org/mailman/listinfo/python-list

Re: Beginner Question

On Thursday 02 June 2016 14:21, Igor Korot wrote: > Hi, guys, > > On Wed, Jun 1, 2016 at 9:42 PM, boB Stepp <robertvst...@gmail.com> wrote: >> On Wed, Jun 1, 2016 at 7:55 PM, Marcin Rak <m...@sightlineinnovation.com> >> wrote: >>> Hi to all >>

Re: Beginner Question

Hi, guys, On Wed, Jun 1, 2016 at 9:42 PM, boB Stepp <robertvst...@gmail.com> wrote: > On Wed, Jun 1, 2016 at 7:55 PM, Marcin Rak <m...@sightlineinnovation.com> > wrote: >> Hi to all >> >> I have a beginner question to which I have not found an answer I was ab

Re: Beginner Question

On Thursday 02 June 2016 10:55, Marcin Rak wrote: > Hi to all > > I have a beginner question to which I have not found an answer I was able to > understand. Could someone explain why the following program: > > def f(a, L=[]): > L.append(a) > return L The d

Re: Beginner Question

On Wed, Jun 1, 2016 at 7:55 PM, Marcin Rak <m...@sightlineinnovation.com> wrote: > Hi to all > > I have a beginner question to which I have not found an answer I was able to > understand. Could someone explain why the following program: > > def f(a, L=[]): >

Beginner Question

Hi to all I have a beginner question to which I have not found an answer I was able to understand. Could someone explain why the following program: def f(a, L=[]): L.append(a) return L print(f(1)) print(f(2)) print(f(3)) gives us the following result: [1] [1,2] [1,2,3] How can

Re: QWERTY was not designed to intentionally slow typists down (was: Unicode normalisation [was Re: [beginner] What's wrong?])

On Monday 18 April 2016 12:01, Random832 wrote: > On Sun, Apr 17, 2016, at 21:39, Steven D'Aprano wrote: >> Oh no, it's the thread that wouldn't die! *wink* >> >> Actually, yes it is. At least, according to this website: >> >> http://www.mit.edu/~jcb/Dvorak/history.html > > I'd really rather

Re: QWERTY was not designed to intentionally slow typists down (was: Unicode normalisation [was Re: [beginner] What's wrong?])

On Mon, Apr 18, 2016 at 11:39 AM, Steven D'Aprano wrote: > With QWERTY, the eight home keys only cover a fraction over a quarter of > all key presses: ASDF JKL; have frequencies of > > 8.12% 6.28% 4.32% 2.30% 0.10% 0.69% 3.98% and effectively 0% > > making a total of 25.79%.

Re: QWERTY was not designed to intentionally slow typists down (was: Unicode normalisation [was Re: [beginner] What's wrong?])

On Sun, Apr 17, 2016, at 21:39, Steven D'Aprano wrote: > Oh no, it's the thread that wouldn't die! *wink* > > Actually, yes it is. At least, according to this website: > > http://www.mit.edu/~jcb/Dvorak/history.html I'd really rather see an instance of the claim not associated with Dvorak

Re: QWERTY was not designed to intentionally slow typists down (was: Unicode normalisation [was Re: [beginner] What's wrong?])

Oh no, it's the thread that wouldn't die! *wink* On Sun, 10 Apr 2016 01:53 am, Random832 wrote: > On Fri, Apr 8, 2016, at 23:28, Steven D'Aprano wrote: >> This is the power of the "slowing typists down is a myth" meme: same >> Wikipedia contributor takes an article which *clearly and obviously*

Re: QWERTY was not designed to intentionally slow typists down (was: Unicode normalisation [was Re: [beginner] What's wrong?])

Ian Kelly on Sun, 10 Apr 2016 07:43:13 -0600 typed in comp.lang.python the following: >On Sat, Apr 9, 2016 at 9:09 PM, pyotr filipivich wrote: >> ASINTOER are the top eight English letters (not in any order, it >> is just that "A Sin To Err"

Re: QWERTY was not designed to intentionally slow typists down (was: Unicode normalisation [was Re: [beginner] What's wrong?])

On Sat, Apr 9, 2016 at 9:09 PM, pyotr filipivich wrote: > ASINTOER are the top eight English letters (not in any order, it > is just that "A Sin To Err" is easy to remember. What's so hard to remember about ETA OIN SHRDLU? Plus that even gives you the top twelve.

Re: Unicode normalisation [was Re: [beginner] What's wrong?]

Steven D'Aprano : But when you get down to fundamentals, character sets and alphabets have always blurred the line between presentation and meaning. W ("double-u") was, once upon a time, UU And before that, it was VV, because the Romans used V the way we now use U, and

Re: Unicode normalisation [was Re: [beginner] What's wrong?]

Ben Bacarisse wrote: The problem with that theory is that 'er/re' (this is e and r in either order) is the 3rd most common pair in English but have been placed together. No, they haven't. The order of the characters in the type basket goes down the slanted columns of keys, so E and R are

Re: QWERTY was not designed to intentionally slow typists down (was: Unicode normalisation [was Re: [beginner] What's wrong?])

Dennis Lee Bieber on Sat, 09 Apr 2016 14:52:50 -0400 typed in comp.lang.python the following: >On Sat, 09 Apr 2016 11:44:48 -0400, Random832 >declaimed the following: > >>I don't understand where this idea that alternating hands makes you >>slows

Re: Unicode normalisation [was Re: [beginner] What's wrong?]

On Sat, Apr 9, 2016, at 12:25 PM, Mark Lawrence via Python-list wrote: > Again, where is the relevance to Python in this discussion, as we're on > the main Python mailing list? Please can the moderators take this stuff > out, it is getting beyond the pale. You need to come to grip with the

RE: [E] QWERTY was not designed to intentionally slow typists down (was: Unicode normalisation [was Re: [beginner] What's wrong?])

-Original Message- From: Ben Finney >> This is an often-repeated myth, with citations back as far as the 1970s. >> It is false. >> The design is intended to reduce jamming the print heads together, but the >> goal of this is not to reduce speed, but to enable *fast* typing. >> It

Re: Unicode normalisation [was Re: [beginner] What's wrong?]

On 09/04/2016 17:08, Rustom Mody wrote: On Saturday, April 9, 2016 at 7:14:05 PM UTC+5:30, Ben Bacarisse wrote: The problem with that theory is that 'er/re' (this is e and r in either order) is the 3rd most common pair in English but have been placed together. ou and et (in either order) are

Re: Unicode normalisation [was Re: [beginner] What's wrong?]

Rustom Mody writes: > On Saturday, April 9, 2016 at 7:14:05 PM UTC+5:30, Ben Bacarisse wrote: >> The problem with that theory is that 'er/re' (this is e and r in either >> order) is the 3rd most common pair in English but have been placed >> together. ou and et (in either

Re: Unicode normalisation [was Re: [beginner] What's wrong?]

On Saturday, April 9, 2016 at 7:14:05 PM UTC+5:30, Ben Bacarisse wrote: > The problem with that theory is that 'er/re' (this is e and r in either > order) is the 3rd most common pair in English but have been placed > together. ou and et (in either order) are the 15th and 22nd most common > and

Re: QWERTY was not designed to intentionally slow typists down (was: Unicode normalisation [was Re: [beginner] What's wrong?])

On Fri, Apr 8, 2016, at 23:28, Steven D'Aprano wrote: > This is the power of the "slowing typists down is a myth" meme: same > Wikipedia contributor takes an article which *clearly and obviously* > repeats the conventional narrative that QWERTY was designed to > decrease the number of key presses

Re: QWERTY was not designed to intentionally slow typists down (was: Unicode normalisation [was Re: [beginner] What's wrong?])

On Fri, Apr 8, 2016, at 23:28, Steven D'Aprano wrote: > And how did it enable fast typing? By *slowing down the typist*, and thus > having fewer jams. Er, no? The point is that type bars that are closer together collide more easily *at the same actual typing speed* than ones that are further

Re: Unicode normalisation [was Re: [beginner] What's wrong?]

Ben Bacarisse writes: > alister writes: > >> >> the design of qwerty was not to "Slow" the typist bu to ensure that the >> hammers for letters commonly used together are spaced widely apart, >> reducing the portion of trier travel arc were

Re: Unicode normalisation [was Re: [beginner] What's wrong?]

alister writes: > > the design of qwerty was not to "Slow" the typist bu to ensure that the > hammers for letters commonly used together are spaced widely apart, > reducing the portion of trier travel arc were the could jam. > I and E are actually such a pair which

Re: Unicode normalisation [was Re: [beginner] What's wrong?]

On Fri, 08 Apr 2016 20:20:02 -0400, Dennis Lee Bieber wrote: > On Fri, 8 Apr 2016 11:04:53 -0700 (PDT), Rustom Mody > declaimed the following: > >>Its reasonably likely that all our keyboards start QWERT... >> Doesn't make it a sane design. >> > It was a sane design

Re: QWERTY was not designed to intentionally slow typists down (was: Unicode normalisation [was Re: [beginner] What's wrong?])

On Sat, 9 Apr 2016 10:43 am, Ben Finney wrote: > Dennis Lee Bieber writes: > >> [The QWERTY keyboard layout] was a sane design -- for early mechanical >> typewrites. It fulfills its goal of slowing down a typist to reduce >> jamming print-heads at the platen. > > This is

QWERTY was not designed to intentionally slow typists down (was: Unicode normalisation [was Re: [beginner] What's wrong?])

Dennis Lee Bieber writes: > [The QWERTY keyboard layout] was a sane design -- for early mechanical > typewrites. It fulfills its goal of slowing down a typist to reduce > jamming print-heads at the platen. This is an often-repeated myth, with citations back as far as the

Re: [beginner] What's wrong?

On 08/04/2016 23:59, sohcahto...@gmail.com wrote: On Friday, April 1, 2016 at 3:57:40 PM UTC-7, Mark Lawrence wrote: On 01/04/2016 23:44, sohcahto...@gmail.com wrote: On Friday, April 1, 2016 at 3:10:51 PM UTC-7, Michael Okuntsov wrote: Nevermind. for j in range(1,8) should be for j in

Re: [beginner] What's wrong?

On Friday, April 1, 2016 at 3:57:40 PM UTC-7, Mark Lawrence wrote: > On 01/04/2016 23:44, sohcahto...@gmail.com wrote: > > On Friday, April 1, 2016 at 3:10:51 PM UTC-7, Michael Okuntsov wrote: > >> Nevermind. for j in range(1,8) should be for j in range(8). > > > > I can't tell you how many times

Re: Unicode normalisation [was Re: [beginner] What's wrong?]

Steven D'Aprano : > But when you get down to fundamentals, character sets and alphabets have > always blurred the line between presentation and meaning. W ("double-u") > was, once upon a time, UU But as every Finnish-speaker now knows, "w" is only an old-fashioned

Re: Unicode normalisation [was Re: [beginner] What's wrong?]

On Sat, 9 Apr 2016 03:21 am, Peter Pearson wrote: > On Fri, 08 Apr 2016 16:00:10 +1000, Steven D'Aprano > wrote: >> On Fri, 8 Apr 2016 02:51 am, Peter Pearson wrote: >>> >>> The Unicode consortium was certifiably insane when it went into the >>> typesetting business. >> >>

Re: Unicode normalisation [was Re: [beginner] What's wrong?]

Adding link On Friday, April 8, 2016 at 11:48:07 PM UTC+5:30, Rustom Mody wrote: > 5.12 Deprecation > > In the Unicode Standard, the term deprecation is used somewhat differently > than it is in some other standards. Deprecation is used to mean that a > character or other feature is strongly

Re: Unicode normalisation [was Re: [beginner] What's wrong?]

On Friday, April 8, 2016 at 11:33:38 PM UTC+5:30, Peter Pearson wrote: > On Sat, 9 Apr 2016 03:50:16 +1000, Chris Angelico wrote: > > On Sat, Apr 9, 2016 at 3:44 AM, Marko Rauhamaa wrote: > [snip] > >> (As for ligatures, I understand that there might be quite a bit of > >> legacy software that

Re: Unicode normalisation [was Re: [beginner] What's wrong?]

On Friday, April 8, 2016 at 11:14:21 PM UTC+5:30, Marko Rauhamaa wrote: > Peter Pearson : > > > On Fri, 08 Apr 2016 16:00:10 +1000, Steven D'Aprano wrote: > >> They are not, and never have been, in the typesetting business. > >> Perhaps characters are not the only things easily confused *wink* >

Re: Unicode normalisation [was Re: [beginner] What's wrong?]

On Sat, 9 Apr 2016 03:50:16 +1000, Chris Angelico wrote: > On Sat, Apr 9, 2016 at 3:44 AM, Marko Rauhamaa wrote: [snip] >> (As for ligatures, I understand that there might be quite a bit of >> legacy software that dedicated code points and code pages for

Re: Unicode normalisation [was Re: [beginner] What's wrong?]

On Friday, April 8, 2016 at 10:24:17 AM UTC+5:30, Chris Angelico wrote: > On Fri, Apr 8, 2016 at 2:43 PM, Rustom Mody wrote: > > No I am not clever/criminal enough to know how to write a text that is > > visually > > close to > > print "Hello World" > > but is internally closer to > > rm -rf / >

Re: Unicode normalisation [was Re: [beginner] What's wrong?]

On Sat, Apr 9, 2016 at 3:44 AM, Marko Rauhamaa wrote: > Unicode heroically and definitively solved the problems ASCII had posed > but introduced a bag of new, trickier problems. > > (As for ligatures, I understand that there might be quite a bit of > legacy software that

Re: Unicode normalisation [was Re: [beginner] What's wrong?]

Peter Pearson : > On Fri, 08 Apr 2016 16:00:10 +1000, Steven D'Aprano > wrote: >> They are not, and never have been, in the typesetting business. >> Perhaps characters are not the only things easily confused *wink* > > Defining codepoints that

Re: Unicode normalisation [was Re: [beginner] What's wrong?]

On Fri, 08 Apr 2016 16:00:10 +1000, Steven D'Aprano wrote: > On Fri, 8 Apr 2016 02:51 am, Peter Pearson wrote: >> >> The Unicode consortium was certifiably insane when it went into the >> typesetting business. > > They are not, and never have been, in the typesetting

Re: From email addresses sometimes strange on this list - was Re: [beginner] What's wrong?

On 05Apr2016 08:58, Chris Angelico wrote: On Tue, Apr 5, 2016 at 8:55 AM, Michael Torrie wrote: Usenet-orginating posts look fine. For example: From: Marko Rauhamaa Newsgroups: comp.lang.python Whereas email ones are sometimes looking

Re: Unicode normalisation [was Re: [beginner] What's wrong?]

On Fri, Apr 8, 2016 at 4:00 PM, Steven D'Aprano wrote: > Or for that matter: > > a = akjhvciwfdwkejfc2qweoduycwldvqspjcwuhoqwe9fhlcjbqvcbhsiauy37wkg() + 100 > b = 100 + akjhvciwfdwkejfc2qweoduycwldvqspjcwuhoqew9fhlcjbqvcbhsiauy37wkg() > > How easily can you tell them apart at

Re: Unicode normalisation [was Re: [beginner] What's wrong?]

On Fri, 8 Apr 2016 02:51 am, Peter Pearson wrote: > Seriously, it's cute how neatly normalisation works when you're > watching closely and using it in the circumstances for which it was > intended, but that hardly proves that these practices won't cause much > trouble when they're used more

Re: Unicode normalisation [was Re: [beginner] What's wrong?]

On Fri, Apr 8, 2016 at 2:43 PM, Rustom Mody wrote: > No I am not clever/criminal enough to know how to write a text that is > visually > close to > print "Hello World" > but is internally closer to > rm -rf / > > For me this: > >>> Α = 1 A = 2 Α + 1 == A > True

Re: Unicode normalisation [was Re: [beginner] What's wrong?]

On Friday, April 8, 2016 at 10:13:16 AM UTC+5:30, Rustom Mody wrote: > No I am not clever/criminal enough to know how to write a text that is > visually > close to > print "Hello World" > but is internally closer to > rm -rf / > > For me this: > >>> Α = 1 > >>> A = 2 > >>> Α + 1 == A > True >

Re: Unicode normalisation [was Re: [beginner] What's wrong?]

On Thursday, April 7, 2016 at 10:22:18 PM UTC+5:30, Peter Pearson wrote: > On Thu, 07 Apr 2016 11:37:50 +1000, Steven D'Aprano wrote: > > On Thu, 7 Apr 2016 05:56 am, Thomas 'PointedEars' Lahn wrote: > >> Rustom Mody wrote: > > > >>> So here are some examples to illustrate what I am saying: > >>>

Re: Unicode normalisation [was Re: [beginner] What's wrong?]

On Fri, Apr 8, 2016 at 2:51 AM, Peter Pearson wrote: > The pile-of-poo character was just frosting on > the cake. > > (Sorry to leave you with that image.) No. You're not even a little bit sorry. You're an evil, evil man. And funny. ChrisA who knows that its

Re: Unicode normalisation [was Re: [beginner] What's wrong?]

On Thu, 07 Apr 2016 11:37:50 +1000, Steven D'Aprano wrote: > On Thu, 7 Apr 2016 05:56 am, Thomas 'PointedEars' Lahn wrote: >> Rustom Mody wrote: > >>> So here are some examples to illustrate what I am saying: >>> >>> Example 1 -- Ligatures: >>> >>> Python3 gets it right >> flag = 1 >>

Re: Unicode normalisation [was Re: [beginner] What's wrong?]

Steven D'Aprano : > So even in English, capitalisation can make a semantic difference. It can even make a pronunciation difference: polish vs Polish. Marko -- https://mail.python.org/mailman/listinfo/python-list

Unicode normalisation [was Re: [beginner] What's wrong?]

On Thu, 7 Apr 2016 05:56 am, Thomas 'PointedEars' Lahn wrote: > Rustom Mody wrote: >> So here are some examples to illustrate what I am saying: >> >> Example 1 -- Ligatures: >> >> Python3 gets it right > flag = 1 > flag >> 1 Python identifiers are intentionally normalised to reduce

Re: [beginner] What's wrong?

On Thu, Apr 7, 2016 at 5:56 AM, Thomas 'PointedEars' Lahn wrote: >> Example 1 -- Ligatures: >> >> Python3 gets it right > flag = 1 > flag >> 1 > > Fascinating; confirmed with > > | $ python3 > | Python 3.4.4 (default, Jan 5 2016, 15:35:18) > | [GCC 5.3.1 20160101] on

Re: [beginner] What's wrong?

Rustom Mody wrote: > On Sunday, April 3, 2016 at 5:17:36 PM UTC+5:30, Thomas 'PointedEars' Lahn > wrote: >> Rustom Mody wrote: >> > When python went to full unicode identifers it should have also added >> > pragmas for which blocks the programmer intended to use -- something >> > like a charset

Re: From email addresses sometimes strange on this list - was Re: [beginner] What's wrong?

On 04/04/2016 04:58 PM, Chris Angelico wrote: > O That probably explains it. It's because of Yahoo and mailing > lists. Yahoo did stuff that breaks stuff, so Mailman breaks stuff > differently to make sure that only Yahoo people get messed up a bit. > It means their names and addresses get

Re: From email addresses sometimes strange on this list - was Re: [beginner] What's wrong?

On Tue, Apr 5, 2016 at 8:55 AM, Michael Torrie wrote: > Usenet-orginating posts look fine. For example: > > From: Marko Rauhamaa > Newsgroups: comp.lang.python > > Whereas email ones are sometimes looking like this: > > From: Mark Lawrence via Python-list

  1   2   3   4   5   6   7   8   9   10   >