import-module

I'd like to know whats is the difference between the memory usage when importing modules in these ways: import Mod1 from Mod1 import * from Mod1 import a,b,c Mainly between the first two. The first uses the least memory since it only creates a single name in the module scope. The second uses the most (assuming Mod1 contains more than just a , b , and c either explicitly or in __all__ ) since all names are recreated. In all three cases the entire module is imported and executed, so if you're looking for large memory savings this is not what you want to optimize. 来源： https://stackoverflow.com

I'm new to Pythonanywhere and want to install the 'soundcloud' Python module. I've opened up a Bash console and given the pip install --user soundcloud command. It appears to have installed, as I see it in the list of modules when I used pip freeze in the Bash console. However, when I open up a Python 2.7 console and try import soundcloud , I get an error message saying that the Soundcloud module does not exist. Any ideas on why this is happening? You've installed soundcloud for 2.6, but you're trying to use it in 2.7. From the FAQ : We've included both easy_install and pip for Python versions

ConfigParser is the much debated vanilla configuration parser for Python. However you can simply import config where config.py has python code which sets configuration parameters. What are the pros\cons of these two approaches of configuration? When should I choose each? The biggest issue I see with import config is that you don't know what will happen when you import it. Yes, you will get a set of symbols that are naturally referenced using a . style interface. But the code in the configuration file can also do who-knows-what. Now, if you completely trust your users, then allowing them to do

If I want to separate out some of my functionality from my main PowerShell script, I can either write that as a .ps1 file and dot source the same or I can create that as a .psm1 and import the same using Import-Module . Which one is better and why? Modules are best for libraries. They give you more control over what is exported from the module. That is by default all script variables in a PSM1 file are private - not visible outside the module when it's imported. Likewise, all functions are public. However, you can use Export-ModuleMember in your PSM1 file to control exactly what variables,

Powershell has two means for importing additional cmdlets into a session, Add-PsSnapIn and Import-Module. The docs are not at all clear regarding when one would chose one over the other. Does anybody know the difference between these? Modules came about in PowerShell V2. V2 can still load Snapins though, if necessary. The big difference is that modules can be deployed using Xcopy. There is no need to register anything. To deploy a Snapin, an installer would have to hack the registry, which would require elevated priveleges. To load a module, you simply have to use the Import-Module command.

I am using the standard TFS vNext build step to execute a PowerShell script. Inside the script I am trying to take advantage of some of the functions within the standard TFS Agent modules. Listed here: http://blog.majcica.com/2015/11/14/available-modules-for-tfs-2015-build-tasks/ I have seen the following two lines in many PowerShell scripts found in the build steps: Import-Module "Microsoft.TeamFoundation.DistributedTask.Task.Internal" Import-Module "Microsoft.TeamFoundation.DistributedTask.Task.Common" I have tried to use the same lines in my script, however I get the error: VERBOSE: Loading