Filenames conflict with IPython kernel about ipykernel HOT 2 CLOSED

I think the kernel is erroneously trying to import modules.

Well, it's certainly trying to import modules. But that's not really erroneous - it's Python code, it can't do much without importing modules.

We've discussed this before. There is a potential way to avoid it: you can start the kernel with a different working directory, passing it the real working directory in some way, and then have it change to that directory once it's finished starting up. However, it would be a bit tricky to do that now that there are multiple different kernels, none of which currently support such a thing. And since it's generally considered a bad idea to give Python files the same name as common modules, we decided not to implement that for the time being.

from ipykernel.

I understand, @takluyver. I found this by accident because I was learning about decorators in Python with examples, using a file called decorator.py. But you're definitely right; I'll just rename my file. 😌

Thank you for your prompt reply.

from ipykernel.