CODEWITHSUNDEEP
pythonbashterminal
Jake
Jake

Reputation: 7782

Python equivalent of ~/.bashrc

For those unfamiliar with ~/.bashrc, it is a customizable script that exists for the Unix shell Bash. When a new terminal session begins, this user-specific file is run. Users can script common variables, functions, and environment settings in this file and thus have them automatically loaded whenever they open a terminal window.

Does something analogous exist for Python? Essentially I would like to define a handful of global Python functions in a script and ensure that they are loaded whenever I run a Python script on my machine, or whenever I start a Python terminal. I am wondering if this behavior already exists, or if there is a straight-forward way to implement it.

Upvotes: 15

Views: 7182

Answers (3)

ROGUH
ROGUH

Reputation: 661

Essentially I would like to define a handful of global Python functions in a script and ensure that they are loaded whenever I run a python script on my machine, or whenever I start a Python terminal

Let's talk about your second option. There are ways to load functions and variables when you start a terminal. I'd recommend using IPython instead of the default Python terminal. However, to do this without installing IPython, modify the environment variable PYTHONSTARTUP. You do lose the ability to compartmentalize your config files.

Once you install IPython, you'll need to initialize its configuration files. To create the default profile:

ipython profile create

To address the common topic in the other answers, global variables and functions are a bad idea especially if they're implicitly defined. However, you can define and load separate config files when starting ipython. To create such a profile:

ipython profile create <name>

To load the <name> profile:

ipython --profile=<name>

Now to modify the config files. Run this command to see where they are:

ipython locate profile

You should find ipython_config.py. I'd suggest reading it, it has very helpful comments.

But to get to the point, you can load arbitrary functions and variables when starting ipython by adding these lines to the config file:

c.InteractiveShellApp.exec_lines = [ "def p(s): print s" ]
c.InteractiveShellApp.exec_files = [ "/path/of/script.py" ]

I'm referencing the IPython docs and the comments in ipython_config.py:

96  # List of files to run at IPython startup.                                      
97  # c.TerminalIPythonApp.exec_files = []                                          
98                                                                                 
99  # lines of code to run at IPython startup.                                      
100 # c.TerminalIPythonApp.exec_lines = []

Upvotes: 6

Charles Duffy
Charles Duffy

Reputation: 295650

This is a bad idea -- don't do it. Really. (Namespace pollution is a serious problem, and you do nobody any favors by writing code that only works on your own machines and nowhere else; by contrast, if you package up your code in a module, you can publish and distribute it properly).

However, if you insist, see the site module, and particular its user-customization behavior:

After this, an attempt is made to import a module named usercustomize, which can perform arbitrary user-specific customizations, if ENABLE_USER_SITE is true. This file is intended to be created in the user site-packages directory (see below), which is part of sys.path unless disabled by -s. An ImportError will be silently ignored.

Thus, you can create a usercustomize module that hotpatches to your heart's content.

As an example of such hotpatching:

def myfunc():
  print 'hello'

main_ns = __import__('__main__')
main_ns.myfunc = myfunc

Upvotes: 6

ShadowRanger
ShadowRanger

Reputation: 155506

Running for every Python script isn't a good idea since it breaks namespacing; per Zen of Python:

Namespaces are one honking great idea -- let's do more of those!

That said, __init__.py can be used to ensure certain code is run if a package or its children are imported, and for customizing the interactive interpreter, set the PYTHONSTARTUP environment variable to point to a file with Python commands to run before handing off to the interactive interpreter, e.g. export PYTHONSTARTUP=$HOME/.pythonrc.

Just make sure the PYTHONSTARTUP file contains legal syntax for both Py2 and Py3 because there is no PYTHON3STARTUP, it'll be run for both versions of Python.

Upvotes: 8

Related Questions