Re: having trouble with virtualenvwrapper - need to run 'source ~/.profile' every time.

Yah, was having trouble installing it within the virtualenv as well, though - ultimately, exiting the virtualenv and installing python-dev allowed me to install the mysqldb module (library? I'm still unclear on terms, sorry). anyways, problem is solved. :> On Thu, Oct 17, 2013 at 9:14 AM, Bill

Re: having trouble with virtualenvwrapper - need to run 'source ~/.profile' every time.

If you installed python-mysqldb in the base python, perhaps by using synaptic, then you aren't supposed to see it in the virtualenv. On Wed, Oct 16, 2013 at 6:48 PM, J. Paskaruk wrote: > Heh, just realized I made an out-of-context comment. This problem is > actually

Re: having trouble with virtualenvwrapper - need to run 'source ~/.profile' every time.

Heh, just realized I made an out-of-context comment. This problem is actually solved, but I'm currently also having trouble connecting to MySQL, and am discussing that in another thread. Forgot which thread I'm in. The potentially virtualenv-based problem is that python-mysqldb is installed, but

Re: having trouble with virtualenvwrapper - need to run 'source ~/.profile' every time.

And just a reminder that you can certainly use virtualenv without virtualenvwrapper. Every env you create with virtualenv will have a script to activate that env located at envname/bin/activate. For example: Open your shell, cd to the desired directory, and create a new env: $ virtualenv

Re: having trouble with virtualenvwrapper - need to run 'source ~/.profile' every time.

virtualenv is, indeed, great stuff, and is unlikely to be your problem. On Wed, Oct 16, 2013 at 3:24 PM, J. Paskaruk wrote: > I will keep that in mind for sure - I'm always aware that there are little > subtleties like that all around me, waiting to trip me up, so when

Re: having trouble with virtualenvwrapper - need to run 'source ~/.profile' every time.

I will keep that in mind for sure - I'm always aware that there are little subtleties like that all around me, waiting to trip me up, so when someone explains one to me, I cleave to the info. I'm pretty paranoid about this kind of thing to begin with, which is why I removed it from the one when I

Re: having trouble with virtualenvwrapper - need to run 'source ~/.profile' every time.

Not strictly true. .bashrc will get run again in a sub-shell. For example, in your shell, you run a command, and that command is a shell script. A new shell is started to run that script. It inherits your environment variables. But it also runs .bashrc. That's usually not a problem, but

Re: having trouble with virtualenvwrapper - need to run 'source ~/.profile' every time.

Ahh k. I took it out of .profile entirely and put it in .bashrc, so it should only be run the once. I'm the only significant user of this computer. Cheers! On Wed, Oct 16, 2013 at 11:45 AM, Bill Freeman wrote: > What I mean by "I don't know about sourceing

Re: having trouble with virtualenvwrapper - need to run 'source ~/.profile' every time.

What I mean by "I don't know about sourceing virtualenvwrapper.sh" is that I don't know, and don't have the inclination to research, whether, having sourced the file in a shell, you should avoid sourcing it again in a sub-shell. What I mean by guard variables is that you could, at the end of your

Re: having trouble with virtualenvwrapper - need to run 'source ~/.profile' every time.

That's the one, thank you so much! I saw in the comments of .profile that it would not be read if there was a .bashrc file present, so my next step was creating that file and putting those lines in it, but I'm very afraid of pooching my install. Noob, like I said. :> I have Aspergers, so I'm not

Re: having trouble with virtualenvwrapper - need to run 'source ~/.profile' every time.

The file you want (assuming that your shell is bash) is .bashrc because it is run every time a bash shell is started, even if it is not a login shell. Note, however, that settings that shouldn't be done multiple times, such as appending ":$HOME/bin" to the PATH, should be protected with an if so

Re: having trouble with virtualenvwrapper - need to run 'source ~/.profile' every time.

Does gnome-terminal make sense to you in this context? I popped up "edit" on the terminal launcher and that's in the Application field. I would, theoretically, add whatever option for gnome-terminal specifies it as a login shell? Testing this, I added --login to the field, per

Re: having trouble with virtualenvwrapper - need to run 'source ~/.profile' every time.

On 10/16/13 8:29 AM, Jimmy Pants wrote: ...every time I open a terminal, that is. As I understand it, .profile is the file to edit in Linux Mint, and it does exist, with some basic code in it, in my home dir. So, per this tutorial

having trouble with virtualenvwrapper - need to run 'source ~/.profile' every time.

...every time I open a terminal, that is. As I understand it, .profile is the file to edit in Linux Mint, and it does exist, with some basic code in it, in my home dir. So, per this tutorial, I added the following to .profile: