ravel and unravel are synonyms
See original GitHub issueRavel and unravel are synonyms, but the methods where they appear accomplish inverse operations. See my SO question for details and example.
Can you consider introducing alternative methods that contain unravel
in their name (even functions containing ravel are IMHO not a happy choice)?
I propose to change e.g.
before | after |
---|---|
unravel_index() |
index_to_coord() |
ravel_multi_index() |
index_to_flat |
Issue Analytics
- State:
- Created 8 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
46 Synonyms & Antonyms for UNRAVEL - Thesaurus.com
unravel ; undo · disentangle · free · separate · unknot · unsnarl · unwind ; decipher · resolve · solve · undo...
Read more >Synonyms of ravel - Merriam-Webster Thesaurus
Synonyms for RAVEL: unravel, unwind, unsnarl, untangle, disentangle, unbraid, unlace, untie; Antonyms of RAVEL: bind, tie, knot, fasten, wind, lash, braid, ...
Read more >Terms Ravel out and Unravel have similar meaning
Mutual synonyms · unwind · undo · disentangle · untangle · untie · ravel · unroll · fray.
Read more >What is the difference between 'ravel' and 'unravel'? - Quora
First note that no one uses the word "ravel" these days (except maybe in knitting or something), but "unravel" is common. Anything that...
Read more >Ravel - Definition, Meaning & Synonyms - Vocabulary.com
verb. disentangle. synonyms: ravel out, unravel. see moresee less. Antonyms: knot, tangle. tangle or complicate · verb. tangle or complicate. “a ravelled story”....
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Python is not a stranger to duality, see 2.* and 3.* and all the burden it imposes with the virtual environments etc… Hence, chances are that even without this renaming, a script written 10 years ago won’t work with the new release of the language. But then, of course, less hassle is always preferable.
I’ll just leave my last two cents on the matter, as a potential workflow, and we can close this issue afterwards:
With a deprecation plan, the changes all happen now, the development continues inside the newly renamed function and when the deadline hits, in 10 years, you just do not package it anymore.
Two years is a short time, 1.7.1 was released 2 yrs ago (the newest RHEL has it), and ubuntu 12LTS is still at 1.6.2 from 4 years ago. Now, imagine running a script you wrote 10 years ago, and having to fix multiple of these renamed functions.
Although there’s no policy about exactly on this, I would personally prefer to avoid changes unless there is a pressing need to make them.