BERJAYA

Re: From JoyceUlysses.txt -- words occurring exactly once
by HenHanna June 9, 2024

June 9, 2024

On 5/30/2024 2:18 PM, dn wrote: > On 31/05/24 08:03, HenHanna via Python-list wrote: >> >> Given a text file of a novel (JoyceUlysses.txt) ... >> >> could someone give me a pretty fast (and simple) Python program that'd >> give me a list of all words occurring exactly once? >> >> -- Also, a list of words occurring once, twice or 3 times >> >> >> >> re: hyphenated words (you can treat it anyway you like) >> >> but ideally, i'd treat [editor-in-chief] >> [go-ahead] [pen-knife] >> [know-how] [far-fetched] ... >> as one unit. > > Split into words - defined as you will. > Use Counter. > > Show some (of your) code and we'll be happy to critique... hard to decide what to do with hyphens and apostrophes (I'd, he's, can't, haven't, A's and B's) 2-step-Process 1. make a file listing all words (one word per line) 2. then, doing the counting. using from collections import Counter Related code (for 1) that i'd used before: Rfile = open("JoyceUlysses.txt", 'r') with open( 'Out.txt', 'w' ) as fo: for line in Rfile: line = line.rstrip() wLis = line.split() for w in wLis: if w != "": w = w.rstrip(";:,'\"[]()*&^%$#(a)!,./<>?_-+=") w = w.lstrip(";:,'\"[]()*&^%$#(a)!,./<>?_-+=") fo.write(w.lower()) fo.write('\n')

8 12

From JoyceUlysses.txt -- words occurring exactly once
by HenHanna June 1, 2024

June 1, 2024

Given a text file of a novel (JoyceUlysses.txt) ... could someone give me a pretty fast (and simple) Python program that'd give me a list of all words occurring exactly once? -- Also, a list of words occurring once, twice or 3 times re: hyphenated words (you can treat it anyway you like) but ideally, i'd treat [editor-in-chief] [go-ahead] [pen-knife] [know-how] [far-fetched] ... as one unit.

7 6

Lprint = ( Lisp-style printing ( of lists and strings (etc.) ) in Python )
by HenHanna June 1, 2024

June 1, 2024

;;; Pls tell me about little tricks you use in Python or Lisp. [('the', 36225), ('and', 17551), ('of', 16759), ('i', 16696), ('a', 15816), ('to', 15722), ('that', 11252), ('in', 10743), ('it', 10687)] ((the 36225) (and 17551) (of 16759) (i 16696) (a 15816) (to 15722) (that 11252) (in 10743) (it 10687)) i think the latter is easier-to-read, so i use this code (by Peter Norvig) def lispstr(exp): # "Convert a Python object back into a Lisp-readable string." if isinstance(exp, list): return '(' + ' '.join(map(lispstr, exp)) + ')' else: return str(exp) def Lprint(x): print(lispstr(x))

2 1

Re: Any marginally usable programming language approaches an ill defined barely usable re-implementation of half of Common-Lisp
by HenHanna May 30, 2024

May 30, 2024

On 5/27/2024 1:59 PM, 2QdxY4RzWzUUiLuE(a)potatochowder.com wrote: > On 2024-05-27 at 12:37:01 -0700, > HenHanna via Python-list <python-list(a)python.org> wrote: > >> >> On 5/27/2024 7:18 AM, Cor wrote: >>> Some entity, AKA "B. Pym" <No_spamming(a)noWhere_7073.org>, >>> wrote this mindboggling stuff: >>> (selectively-snipped-or-not-p) >>> >>>> On 12/16/2023, cor(a)clsnet.nl wrote: >>>> >>>>> Any marginally usable programming language approaches an ill >>>>> defined barely usable re-implementation of half of common-lisp >>>> >>>> The good news is, it's not Lisp that sucks, but Common Lisp. >>>> --- Paul Graham >>> >>> Just to set the record straight; >>> This is not My line. >>> I quoted it but don't know who the originator of that remark is. > > https://en.wikipedia.org/wiki/Greenspun%27s_tenth_rule interesting!!! Are the Rules 1--9 by Greenspun good too? does Greenspun pun ?

3 2

Serializing pydantic enums
by Larry Martell May 29, 2024

May 29, 2024

Just getting started with pydantic. I have this example code: class FinishReason(Enum): stop = 'stop' class Choice(BaseModel): finish_reason: FinishReason = Field(...) But I cannot serialize this: json.dumps(Choice(finish_reason=FinishReason.stop).dict()) *** TypeError: Object of type FinishReason is not JSON serializable I get the object not the value: (Pdb) Choice(finish_reason=FinishReason.stop) Choice(finish_reason=<FinishReason.stop: 'stop'>) Also tried it with .value, same result. What am I missing here?

3 4

Re: SOLVED! Re: Weird Stuff (Markdown, syntax highlighting and Python)
by dn May 29, 2024

May 29, 2024

On 29/05/24 06:49, Gilmeh Serda via Python-list wrote: > > Solved by using a different method. > Hedonist for hire... no job too easy! This combination of sig-file and content seems sadly ironic. How about CONTRIBUTING to the community by explaining 'the solution' to people who may find a similar problem - in the similar manner to the various members who have helped YOU, voluntarily (and despite the paucity of source-information and response)? -- Regards, =dn

1 0

Re: Flubbed it in the second interation through the string: range error... HOW?
by Thomas Passin May 29, 2024

May 29, 2024

On 5/29/2024 8:55 AM, Kevin M. Wilson wrote: > Please recall, I said the format for the email failed to retain the > proper indents. > I'll attach a picture of the code! > Purpose; to uppercase every other letter in a string. > > Thanks all, KMW Simpler is good, and readability is good. For a simple conversion that has a little touch of generality: s1 = 'this is a test' def convert(i, ch): return ch.upper() if i % 2 else ch result = ''.join([convert(i, ch) for i, ch in enumerate(s1)]) print(result) # tHiS Is a tEsT However, this has a weakness: what to do about spaces. Should they be counted among the characters to be uppercased? or should they not be included in the count of the alternation? If you want to uppercase every other letter that is not a space, things become a little more complicated. And then do you want this to apply to all whitespace or only spaces? If you want to skip changing spaces, then you need to track the state of converted characters in some way. It would probably be easier (and more readable) to use a "for x in t:" construction: def convert(convert_this, ch): """Convert character ch if convert_this is True. Don't convert spaces. """ if convert_this: if ch == ' ': return (convert_this, ch) elif convert_this: return (False, ch.upper()) return (True, ch) convert_next = False result = '' for ch in s1: convert_next, ch = convert(convert_next, ch) result += ch print(result) # tHiS Is A TeSt There could be even more complications if you allow non-ascii characters but you were asking about processing character by character so I won't get into that. (You haven't specified the problem in enough detail to answer questions like those). > *************************************************** > "When you pass through the waters, I will be with you: and when you pass > through the rivers, they will not sweep over you. When you walk through > the fire, you will not be burned: the flames will not set you ablaze." > *Isaiah 43:2 > * > > > On Wednesday, May 29, 2024 at 06:19:56 AM MDT, Thomas Passin via > Python-list <python-list(a)python.org> wrote: > > > On 5/29/2024 3:14 AM, Chris Angelico via Python-list wrote: > > On Wed, 29 May 2024 at 16:03, Cameron Simpson via Python-list > > <python-list(a)python.org <mailto:python-list@python.org>> wrote: > >> By which Thomas means stuff like this: > >> > >> print(f'if block {name[index]} and index {index}') > >> > >> Notice the leading "f'". Personally I wouldn't even go that far, just: > >> > >> print('if block', name[index], 'and index', index) > >> > >> But there are plenty of places where f-strings are very useful. > > > > I wouldn't replace str.format() everywhere, nor would I replace > > percent encoding everywhere - but in this case, I think Thomas is > > correct. Not because it's 2024 (f-strings were brought in back in > > 2015, so they're hardly chronologically special), > > I only meant that they have been around for 9 years and are usually more > readable, so just change over already. I had some inertia over them > myself (imagine sticking with % formatting!) so I understand. > > > > but because most of > > this looks like debugging output that can take advantage of this > > feature: > > > > print(f"if block {name[index]=} {index=}") > > > > ChrisA > > -- > https://mail.python.org/mailman/listinfo/python-list > <https://mail.python.org/mailman/listinfo/python-list>

2 2

Flubbed it in the second interation through the string: range error... HOW?
by Kevin M. Wilson May 29, 2024

May 29, 2024

The following is my effort to understand how to process a string, letter, by letter: def myfunc(name): index = 0 howmax = len(name) # while (index <= howmax): while (index < howmax): if (index % 2 == 0): print('letter to upper = {}, index {}!'.format(name[index], index)) name = name[index].upper() print('if block {} and index {}'.format(name[index], index)) elif (index % 2 > 0): print(index) print('Start: elseif block, index is {}, letter is {}'.format(index, name)) # print('letter to lower = {}'.format(name[index])) # print('Already lowercase do noting: name = {}'.format(name[index])) index += 1 # index = name.upper() return name myfunc('capitalism') Error message: Not making sense, index is 1, letter s/b 'a'letter to upper = c, index 0! if block C and index 0 1 Start: elseif block, index is 1, letter is C --------------------------------------------------------------------------- IndexError Traceback (most recent call last) Cell In[27], line 21 17 # index = name.upper() 19 return name ---> 21 myfunc('capitalism') Cell In[27], line 8, in myfunc(name) 6 while (index < howmax): 7 if (index % 2 == 0): ----> 8 print('letter to upper = {}, index {}!'.format(name[index], index)) 9 name = name[index].upper() 10 print('if block {} and index {}'.format(name[index], index)) IndexError: string index out of range*************************************************** So, I'm doing something... Stupid!! *************************************************** "When you pass through the waters, I will be with you: and when you pass through the rivers, they will not sweep over you. When you walk through the fire, you will not be burned: the flames will not set you ablaze." Isaiah 43:2

9 12

Re: SOLVED! Re: Weird Stuff (Markdown, syntax highlighting and Python)
by o1bigtenor May 29, 2024

May 29, 2024

On Tue, May 28, 2024 at 9:48 PM Gilmeh Serda via Python-list < python-list(a)python.org> wrote: > > Solved by using a different method. > > - - - And that was how? TIA

1 0

Any marginally usable programming language approaches an ill defined barely usable re-implementation of half of Common-Lisp
by HenHanna May 27, 2024

May 27, 2024

On 5/27/2024 7:18 AM, Cor wrote: > Some entity, AKA "B. Pym" <No_spamming(a)noWhere_7073.org>, > wrote this mindboggling stuff: > (selectively-snipped-or-not-p) > >> On 12/16/2023, cor(a)clsnet.nl wrote: >> >>> Any marginally usable programming language approaches an ill >>> defined barely usable re-implementation of half of common-lisp >> >> The good news is, it's not Lisp that sucks, but Common Lisp. >> --- Paul Graham > > Just to set the record straight; > This is not My line. > I quoted it but don't know who the originator of that remark is. > > Cor > a few years ago... when i started learning Python... it was so exciting... Every day i thought... --- THis is Lisp in a thin-disguise ... SO Everyone gets it now. Everyone is a Lisper now.

2 1