import libraries from another script

import libraries from another script - Printable Version

+- Python Forum (https://python-forum.io)
+-- Forum: Python Coding (https://python-forum.io/forum-7.html)
+--- Forum: Data Science (https://python-forum.io/forum-44.html)
+--- Thread: import libraries from another script (/thread-11231.html)

import libraries from another script - ankurk017 - Jun-29-2018

I have made a script names libraries.py in which i have written

import datetime as dt
import numpy as np
from netCDF4 import Dataset
import matplotlib as plt
import matplotlib.pyplot as plt

I want to call this script from another script, just to get rid of typing these everytime.
In my second script names script.py, I have written

import libraries
xvals = np.arange(-2, 1, 0.01)

While compiling the second script using python script.py, it is showing error.
The commands in the libraries is compiling well but why can not I use those imported libraries in another function.

RE: import libraries from another script - ichabod801 - Jun-29-2018

The import in libraries.py are importing those packages into the libraries module's name space. To access them after importing libraries, you need to access them from that name space:

xvals = libraries.np.arange(-2, 1, 0.01)

Alternatively, you could star import them, which dumps everything from the libraries name space into the current name space:

from libraries import *
xvals = np.arange(-2, 1, 0.01)

However, this is not recommended. Star imports are opaque as to what they are importing into the current name space, which can cause name conflicts.

Frankly, the correct way to deal with this issue is to just copy and paste those imports to the top of new files. It's actually probably easier than typing "from libraries import *".

RE: import libraries from another script - volcano63 - Jun-29-2018

(Jun-29-2018, 11:29 AM)ichabod801 Wrote: Frankly, the correct way to deal with this issue is to just copy and paste those imports to the top of new files. It's actually probably easier than typing "from libraries import *".

changes out of your control

Not just easier - transient imports should not be relied upon. Someone may change the imports in the module you are importing from - and you, all of a sudden, get an error.

The interpreter does not import objects already in memory, so that there's no impact on memory/performance if you re-import APIs - but your code have better chance of surviving