Lately, I’ve developed a practice of creating an “interact.py” file near the code that I’m working on. I put imports, some magic values, and helpers there that I need while fiddling with things. Then, I just run `$python -i interact.py`. This is my local way of dealing with the same frustration, and I haven’t thought about more general approach yet. That’s interesting.
Hey this is pretty awesome, I didn't know this existed at all. I like your script as well, there are some useful utilities in there. I have two questions:
- On line 266 you say setting this aliases makes JSON NOT valid Python, but I get the feeling it is the other way around. Is that correct? If it works like I think it works then it is a smart trick!
- Do you think I can expect this to work everywhere, or would certain IDEs like Pycharm perhaps use their own startup scripts overwriting my own? Pycharm has a pretty nice built-in REPL for instance.
Lately, I’ve developed a practice of creating an “interact.py” file near the code that I’m working on. I put imports, some magic values, and helpers there that I need while fiddling with things. Then, I just run `$python -i interact.py`. This is my local way of dealing with the same frustration, and I haven’t thought about more general approach yet. That’s interesting.
Hey this is pretty awesome, I didn't know this existed at all. I like your script as well, there are some useful utilities in there. I have two questions:
- On line 266 you say setting this aliases makes JSON NOT valid Python, but I get the feeling it is the other way around. Is that correct? If it works like I think it works then it is a smart trick!
- Do you think I can expect this to work everywhere, or would certain IDEs like Pycharm perhaps use their own startup scripts overwriting my own? Pycharm has a pretty nice built-in REPL for instance.