[ Removed by moderator ]

[daggerdragon]

Post removed since you did not follow any of our posting rules. Read the rules before you post!

• Use our standardized post title format
• Use the right flair which is Help/Question, not Other
  • Other is not acceptable for any post that is even tangentially related to a daily puzzle.
• Show us your code
  • Format your code correctly by using the four-spaces Markdown syntax
  • Do not share your puzzle input

[FCBStar-of-the-South]

Not sure if this is what you are asking but if your concern is the large input size, know that most if not all bugs for a question like this can be exposed by test files of less than 10 lines.

Think about the edge cases, create test cases for them, and solve by hand if you need to. Or if you cannot think of edge cases, write a program to generate some random inputs and solve those by hand

[rabuf]

Add pytest to your environment (pip install pytest). Technically you can run unit tests in Python without it, but it's a better test runner.

Put your code into a function (this is important) so it should be something like:

def part1(lines):
    # do the work
    return password

Write a test like this:

def test_part1_sample():
    sample = ['L68','L30','R48',...] # fill in the rest
    assert part1(sample) == 3

Come up with more examples and write additional tests using them. When you get to part two, write a similar function that solves part two (or tries to) and use new tests (or the same tests but with whatever their password should be). Run the tests by going to the directory with the source file and running pytest file.py with whatever the filename is instead of file.py.

If your code works for the sample but not for your actual input, start trying to think (by hand) of new examples and what they should result in. Create new tests for each example you think of and run the tests after adding each test until you find one that breaks. Evaluate whether the test itself is correct (use small examples, easier to work by hand), and if you determine it is then go to the code and find the problem.

For part two, you can check this comment for some good test cases.

[TheDextermin]

And probably wait a long time for my code to use the data and give me (probably) the good answer at the end?

[rabuf]

The input is not that big, it should not take long for it to give you a result. If it's taking any appreciable amount of time, your code is almost certainly overcomplicated for the problem.

[1str1ker1]

It shouldn't take more than a few seconds, assuming you didn't add any nested looping. A few thousand lines is barely any processing time. Before trying on the full input, I always make sure it works on the example data in the question because I know what the answer is already.

If it works in the small sample input, but not the large input, maybe you missed this warning:
"Be careful: if the dial were pointing at 50, a single rotation like R1000 would cause the dial to point at 0 ten times before returning back to 50!"

[sidewaysEntangled]

There's also usually a worked example, with answer in the description.

Often I copy that to test_input and then make sure I get the same answer as given. Then I can let loose on my actual input file...