2048 is simple, writing a test for your implementation could make your package more robust

[ProsperoKay]

I notice the intention. but i think i can write tests for your code.

Also, it might help in figuring out the /attempt #1 bug

i also discovered a few spelling errors i would like to fix.

I hope it is okay to move ahead with it.

[jwlodek]

Hey, if you would like to contribute tests & fix the typos, a PR would be welcome! If possible, please write the tests to be able to be executed with just

pytest

in the project root directory. Once we have them running I can add CI checks using github actions.

[ProsperoKay]

Hey, if you would like to contribute tests & fix the typos, a PR would be welcome! If possible, please write the tests to be able to be executed with just

pytest

in the project root directory. Once we have them running I can add CI checks using github actions.

Will do

[ProsperoKay]

I have got to admit your implementation of the 2048 is quite complex but i have gotten the pytest command line to work i will push that to you for your review.
After which i will work on the individual test cases

[ProsperoKay]

for #1, I am unable to run py_cui on windows for some reason. When the bug gets fixed, I'll attempt #1.

[jwlodek]

Which error are you getting on windows?

[ProsperoKay]

My issue is py_cui is not running in my terminal cmd. I tried the hello_py_cui example it just doesn't display as expected

I run the example in the terminal
python experiments/cui.py

but it yields no display as it should in the terminal

[ProsperoKay]

I am sure it is a bug for py_cui i will create an issue for that. That is if it hasn't been reported already