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

Place q into builtins? #50

Open
proofit404 opened this issue May 1, 2017 · 2 comments
Open

Place q into builtins? #50

proofit404 opened this issue May 1, 2017 · 2 comments

Comments

@proofit404
Copy link

It is annoying to type import each time I want to use q.

Installation process can setup init hook so q or _q will be available in the global namespace.

Is it desired feature?

@naiveai
Copy link

naiveai commented Nov 16, 2018

Yeah, I personally think this is the main (and pretty much only) disadvantage of q - having to install it each time if you're using virtualenvs, for example. And remembering to uninstall it after you debug or it becomes part of your dependencies.

@merwok
Copy link

merwok commented Nov 16, 2018

That’s a different thing!

The OP requested a way to have the q module automatically imported, the second message is about automatically installing the q package (which is a problem solved by virtualenvwrapper hooks or dev dependencies etc)

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

3 participants