Re: What to write or search on github to get the code for what is written below:

On 2022-01-11 06:31, NArshad wrote: -“How are the relevant cells identified in the spreadsheet?” The column headings are: BOOK_NAME BOOK_AUTHOR BOOK_ISBN TOTAL_COPIES COPIES_LEFT BORROWER’S_NAME ISSUE_DATE RETURN_DATE -“It's often the case that the cells on the first row contain text as column

Re: What to write or search on github to get the code for what is written below:

*** Going back to the post in the thread as I've other concerns (and have turned off the old X-NoArchive setting *** On Thu, 6 Jan 2022 10:55:30 -0800 (PST), NArshad declaimed the following: >All this is going to be in python’s flask and HTML only > >1. First, I have to check in

Re: ast.parse, ast.dump, but with comment preservation?

> > PS: Library is https://github.com/SamuelMarks/cdd-python (might relicense > > with CC0… anyway too early for others to use; wait for the 0.1.0 release ;]) Ended up writing my own CST and added it to that library of mine (link above). My target is adding/removing/changing of: docstrings, funct

Re: What to write or search on github to get the code for what is written below:

-“How are the relevant cells identified in the spreadsheet?” The column headings are: BOOK_NAME BOOK_AUTHOR BOOK_ISBN TOTAL_COPIES COPIES_LEFT BORROWER’S_NAME ISSUE_DATE RETURN_DATE -“It's often the case that the cells on the first row contain text as column labels.” These I have written above

Re: What to write or search on github to get the code for what is written below:

*** Apologies for the repost. Since Gmane made the list a read-only group, I finally broke down and reinstated Giganews comp.lang.python. Unfortunately I'd missed that this came back with X-NoArchive active and Google doesn't even let such messages show up for a day -- so the OP hasn't see

Re: ast.parse, ast.dump, but with comment preservation?

On Thursday, December 16, 2021 at 5:56:51 AM UTC-5, lucas wrote: > Hi ! > > Maybe RedBaron may help you ? > > https://github.com/PyCQA/redbaron > > IIRC, it aims to conserve the exact same representation of the source > code, including comments and empty lines. > > --lucas > On 16/12/2021

Re: preserving entities with lxml

Robin Becker wrote at 2022-1-12 10:22 +: >I have a puzzle over how lxml & entities should be 'preserved' code below >illustrates. To preserve I change & --> & >in the source and add resolve_entities=False to the parser definition. The >escaping means we only have one kind of >entity & which m

preserving entities with lxml

I have a puzzle over how lxml & entities should be 'preserved' code below illustrates. To preserve I change & --> & in the source and add resolve_entities=False to the parser definition. The escaping means we only have one kind of entity & which means lxml will preserve it. For whatever reason lx