-
Notifications
You must be signed in to change notification settings - Fork 28
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Better support for VSC #71
Comments
If dist-packages is in /src there is no need for a pymakr.conf because everything in /src will have to be synced to the MCU. Well except if you want to exclude syncing the pycache directories that are created through 'make test'. But since its only the directories and not their contents its a mere nuisance. |
so are we going to move /dist-packages into /src or not? |
? |
Dear @poesel, we might well consider that in the future. Currently, due to other obligations elsewhere but also within Terkin, I don't think I will able to dedicate myself to that. But in case I would touch that, should we call the directory Apart from that, shall we also put With kind regards, |
I don't think it makes a difference here. So don't change anything. Only creates confusion. Putting the mpys there, too, makes sense (although mpy are not strictly source files :) ). If everything is under one root directory you can sync it with pymakr. No rush. I just wanted to know if we do it or not. |
Now that all code is in /src there is only one step missing to be able to seamlessly use VSC: either move dist-packages into src (there is probaly some thelogical reason not to do this ;) ) or just link the directory into src (that is what I do).
The text was updated successfully, but these errors were encountered: