tqdm VS advent-of-code

yeah my code needs to use multiprocessing, which does not play nice with tqdm. thanks for the tip about positions though, that helped me search more effectively and came up with two promising comments. unmerged / require some workarounds, but might just work:

https://github.com/tqdm/tqdm/issues/1000#issuecomment-184208...

> Like tqdm (Python progressbar library) but as a Unix utility.

FYI: tqdm can be used in a shell pipeline as well. It's documented (at least) in their readme: https://github.com/tqdm/tqdm#module

BTW, my inspiration was https://github.com/tqdm/tqdm library for python and any contribution is welcome to add similar functionality.

I can recommend you the package tqdm (https://github.com/tqdm/tqdm) You can replace the standard for statement with it, or use it with any other iterable. By default, it gives you a progress bar with a percentage and ETA, but you can also configure it to only print the percentage, if you want that. If you want to use print statements, adding \r at the beginning and not putting a line end should also do the trick.

you try to run an python script that requires the tqdm package and also a regex package (what normally should be installed, when installing python). Blender tries to install these packages without success. You probably have to do it on your own by installing them in your pythons virtual environment.

If OP is using python that might be the output of python's tqdm.

I have a client-server socket program where the server sends a file to the client. The server is designed to allow multiple clients using threading. For the file transfer on the client, I am using the tqdm library (https://github.com/tqdm/tqdm).

[LANGUAGE: Python 3] 153/75 Raw solution

One could instead count |F7 (that's what I do in my refactored solution), but counting all the bends would miscount the vertical segments (FJ would end up canceling itself out).

That sounds like what I suggested here, actually. I don't have anything in my library with quite the right API yet, but I already have most of what you describe coded out. (It looks like I whipped it up for 2017 Day 13.)

[LANGUAGE: Python 3] Embarrassing/Embarrassing Ugly raw solution code

[LANGUAGE: Python 3] 66/101 Raw solution code

Python 3 21/12

It doesn't, but you can use a separate list, wrapper classes, and deque.index to find where the values live. I may be biased but I think that my solution (ultimately using deque) isn't as complex as a custom linked list.

Part 2 assumes you did part 1 properly. I did not! I'm pretty sure that the intended solution is to do a sort of reverse search (have a target number of geodes and work backwards to see if that's possible to achieve) but I was just not having success coming up with a way to do that. It's probably going to be blindingly obvious once I figure it out, but that might be an exercise for tomorrow.

Python 3 9/15!!!

Python 3 44/45