Skip to content
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

. is not a valid Python package name #50

Open
fr0der1c opened this issue Dec 19, 2019 · 3 comments
Open

. is not a valid Python package name #50

fr0der1c opened this issue Dec 19, 2019 · 3 comments

Comments

@fr0der1c
Copy link

image

I just installed the plugin and it gives me this error. It's fine if I run the command in terminal:
image

@fr0der1c
Copy link
Author

Sorry. I just found that when I'm in the terminal, I didn't go to the actual project directory in Pycharm. Instead, I went to the parent directory. If I go to the actual project directory in terminal, I will see . is not a valid Python package name again. How to fix this error?

@fr0der1c
Copy link
Author

I just found myself in a dilemma:
My repo (scripts) is a monorepo and there are many subdirectories containing scripts for different usages. Each script has its own dependencies so their Pipfiles are in their own directory. PyCharm only find Pipfile in project root so I have to open the subdirectories as different projects in PyCharm. But the plugin will not work in this way.

scripts
  - script_A
     - Pipfile
     - Pipfile.lock
  - script_B
     - Pipfile
     - Pipfile.lock

@ilevkivskyi
Copy link
Contributor

One possible solution you can try is to modify to the command that plugin runs (right click in plugin window -> Configure plugin...). The plugin configs are stored per-project, so you can have different commands for different projects.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants