For not having to call 'source ...' in a Dockerfile, if you use the python executable from the virtualenv directly, then it will be as if you've activated that virtualenv.
This works because of the relative path to the pyenv.cfg file.
I wonder if you can, under GDPR, request that all your data is deleted and then create a new account. Not allowing you to create a new account could be argued as a violation of GDPR as it would mean that they kept personally identifiable data about you.
Currently the only implementation available is for .Net through the ElectronCgi.DotNet nuget package, but there's no reason for this not to work with other languages/runtimes (it relies on stdin/stdout that is available in all processes).
Did you have a particular language/runtime in mind?
I've been using Anki since 2013 (almost 5 years).
One really nice thing about Anki is that it has analytics. I currently have 4532 cards and my numbers are 99.18% correct answers for "Learning" (very young) cards, 98.44% for Young cards and 92.52% for Mature cards.
No way I would be able to remember over 4000 pieces of information without spaced repetition.
I truly believe this is the best learning "hack" there is.
I've wrote about my experience here: https://www.blinkingcaret.com/2016/05/04/hack-your-brain-lea...
Healthy lifestyle will do wonders for your memory. Try to keep your stress levels down, eat right and sleep well.
Memory can be trained too. Look up Dominic O'Brien or Tony Buzan. Their books are a bit sensationalist, but the techniques work, e.g. you'll quickly be able to memorize a full deck of cards.
Don't know if that kind of training will improve all aspects of memory, but it certainly won't hurt
One thing that should also be emphasized is that there is a great number of PhD candidates that never actually finish, in some universities that number is more than half.
Many of these, before quitting, teach to help pay tuition and do all sorts of tasks for their department/supervisor that are not related or help them finish their PhD.
I'm of the opinion that you should only test public methods (what your class exposes to the outside world, i.e. its contract). Private methods are implementation details and therefore you should be able to change them [effectively changing your implementation, but that should not change how your public methods behave] and rely on the tests you have on your public methods to detect any change in behavior that is not correct.
When you say: "...methods used by a method under test can only be assumed to work if each of those methods has good tests", my opinion is that if that is an issue, than those private methods belong in another class that is a dependency of the class you are testing, and should be tested in the context of that other class.
And that is what I pointed out in the answer, although worded a little differently: "If you use a callback, at the time of the invocation of the asynchronous operation you have to specify how it will be handled, hence the coupling. With promises you can specify how it will be handled later."
This works because of the relative path to the pyenv.cfg file.