[HN Gopher] Show HN: Simple Wordle solver in command line in Python
___________________________________________________________________
Show HN: Simple Wordle solver in command line in Python
Author : fzxu22
Score : 7 points
Date : 2022-01-22 20:55 UTC (2 hours ago)
(HTM) web link (github.com)
(TXT) w3m dump (github.com)
| TheRealNGenius wrote:
| in my opinion, this misses the point of wordle
| fzxu22 wrote:
| You ... are not wrong ;)
| oneoff786 wrote:
| Is Aeros the entropy maximizing first guess?
| fzxu22 wrote:
| Probably true according to this post:
| https://slc.is/#Best%20Wordle%20Strategy%20%E2%80%94%20Explo...
| nanis wrote:
| _Correction_ : I thought this was script to solve Wordle puzzles,
| so I provided a cheat helper below. At first blush, I thought the
| idea was for the human to feed this script information back from
| Wordle so it could improve its guesses. _Sigh_
|
| Also, you really need better names for your methods and
| variables, starting with this bit here:
| https://github.com/KevinXuxuxu/wordle_machine/blob/64a8534ad...
|
| As you think about a better way to name those, you will realize
| it is possible to do this in a much less convoluted way.
|
| Hmmm, I have been using this Perl script:
| #!/usr/bin/env perl use strict; use
| warnings; use feature 'say'; my @words
| = grep # Add conditions below !/^[A-Z]/,
| grep length == 5, map split, do { local $/; <> };
| say for @words
|
| Invoke it from the command line with your word list. I've been
| lazy, so I use `./wg /usr/share/dict/words` which means way more
| options than a more tailored word list would give which means I
| am only cheating a little. So, for example, I type "amber" as my
| first move and I am told "e" is in the wrong spot and none of the
| other letters match, I update the selection using that
| information: my @words = grep # Add conditions
| below !/^...e/ && /e/ &&
| !/[ambr]/ && !/^[A-Z]/, grep length == 5,
| map split, do { local $/; <> };
| fzxu22 wrote:
| Thanks for the reply! I really appreciate your feedback on
| this. I wasn't giving much thought about coding style and
| naming etc. when I worked on this, just wanted to get it
| running asap. I'll definitely take a better look at your
| suggestion (I'm not very familiar with perl) and see if I find
| any time to improve this thing. cheers.
| fzxu22 wrote:
| see README
___________________________________________________________________
(page generated 2022-01-22 23:01 UTC)