Import system python ошибка

asked Jun 15, 2020 at 18:42

you should use this:

import clr

clr.AddReference('System')

from System import String

AngeloAngelo

1,3913 gold badges16 silver badges40 bronze badges

In my Python3, System is not a module — it’s a method of the os module.

so I use

from os import system

then

system("<<Put Your Command Here>>")

If you want it called System with a capital S (maybe for backward compatability with already-written programs?), use

from os import system as System

answered Jul 14, 2020 at 19:54

asked Jun 15, 2020 at 18:42

you should use this:

import clr

clr.AddReference('System')

from System import String

AngeloAngelo

1,3913 gold badges16 silver badges40 bronze badges

In my Python3, System is not a module — it’s a method of the os module.

so I use

from os import system

then

system("<<Put Your Command Here>>")

If you want it called System with a capital S (maybe for backward compatability with already-written programs?), use

from os import system as System

answered Jul 14, 2020 at 19:54

Where did you get this `Clr version 1.0.2`?
Is it this package?

https://pypi.python.org/pypi/clr/1.0.3

If yes, you need to uninstall this clr package to use pythonnet, because
both packages have a name clash.

…

You can also try using importlib to import clr from pythonnet with full
path provided to clr.pyd.

On Thu, Feb 16, 2017, 8:35 PM Denis Akhiyarov <denis.akhiyarov@gmail.com>
wrote:

…

Wow thanks for the quick answer ! Indeed getting rid of clr and reinstalling pyhtonnet fixed the stuff.

Many thanks guys !

In retrospective we should have registered that package name in PyPi

I think there is a way to «complain» to pypi members, so that this clashing is resolved.

This clr package is only about one month old.

But let’s wait over the weekends, if the author responds.

I’ve pinged him again to get to a decision: lmittmann/style#1

In case he does not want to give up the name we should:

• Add information to our README.md that one must make sure that pythonnet installed via pip
• Add the same information to our pypi channel and homepage

In case he does:

• We have to grab the clr name on pypi and essentially alias it to pythonnet, for example by putting a package there that prints a warning and depends on pythonnet

@denfromufa @vmuriart I have added you as owners of the clr package on PyPI. I don’t have the time to finish the work there right now, so here’s the TODO list

• Put up a new package information page that is basically our usual README but adds a disclaimer that the previously listed package is now called style and that the «real» name of the Python.NET package is pythonnet
• Create a small package (i.e. setup.py) within our git-repo that only depends on pythonnet
• Remove the existing clr package and push our alias-package

We may as well reserve Python.net package name on pypi.

I just got this error and found out it was due to having multiple Python installations, including pythonnet package install in each.

1. If, you’re in Windows, do: where.exe python to find where it’s installed.
2. Next, use the version specific pip, like this:

(depending on what you found in (1).)

The version I am using, is conda so scripts installed with conda and using import clr, fails with:
ModuleNotFoundError: No module named 'clr'
when ran from command line.

I don’t know how to fix this.

However, running script in it’s own home directory (elsewhere) seem to work. Very weird!

asked Dec 3, 2008 at 21:26

Based on your comments to orip’s post, I guess this is what happened:

1. You edited __init__.py on windows.
2. The windows editor added something non-printing, perhaps a carriage-return (end-of-line in Windows is CR/LF; in unix it is LF only), or perhaps a CTRL-Z (windows end-of-file).
3. You used WinSCP to copy the file to your unix box.
4. WinSCP thought: «This has something that’s not basic text; I’ll put a .bin extension to indicate binary data.»
5. The missing __init__.py (now called __init__.py.bin) means python doesn’t understand toolkit as a package.
6. You create __init__.py in the appropriate directory and everything works… ?

answered Dec 4, 2008 at 0:17

Does

(local directory)/site-packages/toolkit

have a __init__.py?

To make import walk through your directories every directory must have a __init__.py file.

answered Dec 3, 2008 at 21:50

I ran into something very similar when I did this exercise in LPTHW; I could never get Python to recognise that I had files in the directory I was calling from. But I was able to get it to work in the end. What I did, and what I recommend, is to try this:

(NOTE: From your initial post, I am assuming you are using an *NIX-based machine and are running things from the command line, so this advice is tailored to that. Since I run Ubuntu, this is what I did)

1. Change directory (cd) to the directory above the directory where your files are. In this case, you’re trying to run the mountain.py file, and trying to call the toolkit.interface.py module, which are in separate directories. In this case, you would go to the directory that contains paths to both those files (or in other words, the closest directory that the paths of both those files share). Which in this case is the toolkit directory.

2. When you are in the toolkit directory, enter this line of code on your command line:

   export PYTHONPATH=.

   This sets your PYTHONPATH to «.», which basically means that your PYTHONPATH will now look for any called files within the directory you are currently in, (and more to the point, in the sub-directory branches of the directory you are in. So it doesn’t just look in your current directory, but in all the directories that are in your current directory).

3. After you’ve set your PYTHONPATH in the step above, run your module from your current directory (the toolkit directory). Python should now find and load the modules you specified.

On *nix, also make sure that PYTHONPATH is configured correctly, especially that it has this format:

 .:/usr/local/lib/python

(Mind the .: at the beginning, so that it can search on the current directory, too.)

It may also be in other locations, depending on the version:

 .:/usr/lib/python
 .:/usr/lib/python2.6
 .:/usr/lib/python2.7 and etc.

You are reading this answer says that your __init__.py is in the right place, you have installed all the dependencies and you are still getting the ImportError.

I was facing a similar issue except that my program would run fine when ran using PyCharm but the above error when I would run it from the terminal. After digging further, I found out that PYTHONPATH didn’t have the entry for the project directory. So, I set PYTHONPATH per Import statement works on PyCharm but not from terminal:

export PYTHONPATH=$PYTHONPATH:`pwd`  (OR your project root directory)

There’s another way to do this using sys.path as:

import sys
sys.path.insert(0,'<project directory>') OR
sys.path.append('<project directory>')

You can use insert/append based on the order in which you want your project to be searched.

answered Jan 4, 2017 at 17:53

I solved my own problem, and I will write a summary of the things that were wrong and the solution:

The file needs to be called exactly __init__.py. If the extension is different such as in my case .py.bin then Python cannot move through the directories and then it cannot find the modules. To edit the files you need to use a Linux editor, such as vi or nano. If you use a Windows editor this will write some hidden characters.

Another problem that was affecting it was that I had another Python version installed by the root, so if someone is working with a local installation of python, be sure that the Python installation that is running the programs is the local Python. To check this, just do which python, and see if the executable is the one that is in your local directory. If not, change the path, but be sure that the local Python directory is before than the other Python.

answered Dec 3, 2008 at 21:31

answered Sep 18, 2017 at 15:30

To all those who still have this issue. I believe Pycharm gets confused with imports. For me, when i write ‘from namespace import something’, the previous line gets underlined in red, signaling that there is an error, but works. However »from .namespace import something’ doesn’t get underlined, but also doesn’t work.

Try

try:
    from namespace import something 
except NameError:
    from .namespace import something

answered May 11, 2019 at 19:34

answered Jan 7, 2009 at 14:22

If you have tried all methods provided above but failed, maybe your module has the same name as a built-in module. Or, a module with the same name existing in a folder that has a high priority in sys.path than your module’s.

To debug, say your from foo.bar import baz complaints ImportError: No module named bar. Changing to import foo; print foo, which will show the path of foo. Is it what you expect?

If not, Either rename foo or use absolute imports.

answered May 2, 2017 at 6:41

1. You must have the file __ init__.py in the same directory where it’s the file that you are importing.
2. You can not try to import a file that has the same name and be a file from 2 folders configured on the PYTHONPATH.

eg:
/etc/environment

PYTHONPATH=$PYTHONPATH:/opt/folder1:/opt/folder2

/opt/folder1/foo

/opt/folder2/foo

And, if you are trying to import foo file, python will not know which one you want.

from foo import … >>> importerror: no module named foo

answered Jan 9, 2014 at 19:45

My two cents:

Spit:

Traceback (most recent call last):
      File "bashbash.py", line 454, in main
        import bosh
      File "Wrye Bash Launcher.pyw", line 63, in load_module
        mod = imp.load_source(fullname,filename+ext,fp)
      File "bashbosh.py", line 69, in <module>
        from game.oblivion.RecordGroups import MobWorlds, MobDials, MobICells, 
    ImportError: No module named RecordGroups

This confused the hell out of me — went through posts and posts suggesting ugly syspath hacks (as you see my __init__.py were all there). Well turns out that game/oblivion.py and game/oblivion was confusing python
which spit out the rather unhelpful «No module named RecordGroups». I’d be interested in a workaround and/or links documenting this (same name) behavior -> EDIT (2017.01.24) — have a look at What If I Have a Module and a Package With The Same Name? Interestingly normally packages take precedence but apparently our launcher violates this.

EDIT (2015.01.17): I did not mention we use a custom launcher dissected here.

dukevindukevin

22k36 gold badges80 silver badges110 bronze badges

YuanhuiYuanhui

4595 silver badges15 bronze badges

Linux: Imported modules are located in /usr/local/lib/python2.7/dist-packages

If you’re using a module compiled in C, don’t forget to chmod the .so file after sudo setup.py install.

sudo chmod 755 /usr/local/lib/python2.7/dist-packages/*.so

answered May 30, 2014 at 22:50

answered Sep 4, 2013 at 2:52

answered Mar 27, 2018 at 12:41

michael-slxmichael-slx

6558 silver badges15 bronze badges

juanignaciosljuanignaciosl

3,3952 gold badges26 silver badges28 bronze badges

ioaniatrioaniatr

2774 silver badges15 bronze badges

PoliPoli

7710 bronze badges

GhotiGhoti

7374 silver badges18 bronze badges

After just suffering the same issue I found my resolution was to delete all pyc files from my project, it seems like these cached files were somehow causing this error.

Easiest way I found to do this was to navigate to my project folder in Windows explorer and searching for *.pyc, then selecting all (Ctrl+A) and deleting them (Ctrl+X).

Its possible I could have resolved my issues by just deleting the specific pyc file but I never tried this

RocketqRocketq

5,01420 gold badges75 silver badges123 bronze badges

Toivo SäwénToivo Säwén

1,6732 gold badges14 silver badges33 bronze badges

asked Dec 3, 2008 at 21:26

Based on your comments to orip’s post, I guess this is what happened:

1. You edited __init__.py on windows.
2. The windows editor added something non-printing, perhaps a carriage-return (end-of-line in Windows is CR/LF; in unix it is LF only), or perhaps a CTRL-Z (windows end-of-file).
3. You used WinSCP to copy the file to your unix box.
4. WinSCP thought: «This has something that’s not basic text; I’ll put a .bin extension to indicate binary data.»
5. The missing __init__.py (now called __init__.py.bin) means python doesn’t understand toolkit as a package.
6. You create __init__.py in the appropriate directory and everything works… ?

answered Dec 4, 2008 at 0:17

Does

(local directory)/site-packages/toolkit

have a __init__.py?

To make import walk through your directories every directory must have a __init__.py file.

answered Dec 3, 2008 at 21:50

I ran into something very similar when I did this exercise in LPTHW; I could never get Python to recognise that I had files in the directory I was calling from. But I was able to get it to work in the end. What I did, and what I recommend, is to try this:

(NOTE: From your initial post, I am assuming you are using an *NIX-based machine and are running things from the command line, so this advice is tailored to that. Since I run Ubuntu, this is what I did)

1. Change directory (cd) to the directory above the directory where your files are. In this case, you’re trying to run the mountain.py file, and trying to call the toolkit.interface.py module, which are in separate directories. In this case, you would go to the directory that contains paths to both those files (or in other words, the closest directory that the paths of both those files share). Which in this case is the toolkit directory.

2. When you are in the toolkit directory, enter this line of code on your command line:

   export PYTHONPATH=.

   This sets your PYTHONPATH to «.», which basically means that your PYTHONPATH will now look for any called files within the directory you are currently in, (and more to the point, in the sub-directory branches of the directory you are in. So it doesn’t just look in your current directory, but in all the directories that are in your current directory).

3. After you’ve set your PYTHONPATH in the step above, run your module from your current directory (the toolkit directory). Python should now find and load the modules you specified.

On *nix, also make sure that PYTHONPATH is configured correctly, especially that it has this format:

 .:/usr/local/lib/python

(Mind the .: at the beginning, so that it can search on the current directory, too.)

It may also be in other locations, depending on the version:

 .:/usr/lib/python
 .:/usr/lib/python2.6
 .:/usr/lib/python2.7 and etc.

You are reading this answer says that your __init__.py is in the right place, you have installed all the dependencies and you are still getting the ImportError.

I was facing a similar issue except that my program would run fine when ran using PyCharm but the above error when I would run it from the terminal. After digging further, I found out that PYTHONPATH didn’t have the entry for the project directory. So, I set PYTHONPATH per Import statement works on PyCharm but not from terminal:

export PYTHONPATH=$PYTHONPATH:`pwd`  (OR your project root directory)

There’s another way to do this using sys.path as:

import sys
sys.path.insert(0,'<project directory>') OR
sys.path.append('<project directory>')

You can use insert/append based on the order in which you want your project to be searched.

answered Jan 4, 2017 at 17:53

I solved my own problem, and I will write a summary of the things that were wrong and the solution:

The file needs to be called exactly __init__.py. If the extension is different such as in my case .py.bin then Python cannot move through the directories and then it cannot find the modules. To edit the files you need to use a Linux editor, such as vi or nano. If you use a Windows editor this will write some hidden characters.

Another problem that was affecting it was that I had another Python version installed by the root, so if someone is working with a local installation of python, be sure that the Python installation that is running the programs is the local Python. To check this, just do which python, and see if the executable is the one that is in your local directory. If not, change the path, but be sure that the local Python directory is before than the other Python.

answered Dec 3, 2008 at 21:31

answered Sep 18, 2017 at 15:30

To all those who still have this issue. I believe Pycharm gets confused with imports. For me, when i write ‘from namespace import something’, the previous line gets underlined in red, signaling that there is an error, but works. However »from .namespace import something’ doesn’t get underlined, but also doesn’t work.

Try

try:
    from namespace import something 
except NameError:
    from .namespace import something

answered May 11, 2019 at 19:34

answered Jan 7, 2009 at 14:22

If you have tried all methods provided above but failed, maybe your module has the same name as a built-in module. Or, a module with the same name existing in a folder that has a high priority in sys.path than your module’s.

To debug, say your from foo.bar import baz complaints ImportError: No module named bar. Changing to import foo; print foo, which will show the path of foo. Is it what you expect?

If not, Either rename foo or use absolute imports.

answered May 2, 2017 at 6:41

1. You must have the file __ init__.py in the same directory where it’s the file that you are importing.
2. You can not try to import a file that has the same name and be a file from 2 folders configured on the PYTHONPATH.

eg:
/etc/environment

PYTHONPATH=$PYTHONPATH:/opt/folder1:/opt/folder2

/opt/folder1/foo

/opt/folder2/foo

And, if you are trying to import foo file, python will not know which one you want.

from foo import … >>> importerror: no module named foo

answered Jan 9, 2014 at 19:45

My two cents:

Spit:

Traceback (most recent call last):
      File "bashbash.py", line 454, in main
        import bosh
      File "Wrye Bash Launcher.pyw", line 63, in load_module
        mod = imp.load_source(fullname,filename+ext,fp)
      File "bashbosh.py", line 69, in <module>
        from game.oblivion.RecordGroups import MobWorlds, MobDials, MobICells, 
    ImportError: No module named RecordGroups

This confused the hell out of me — went through posts and posts suggesting ugly syspath hacks (as you see my __init__.py were all there). Well turns out that game/oblivion.py and game/oblivion was confusing python
which spit out the rather unhelpful «No module named RecordGroups». I’d be interested in a workaround and/or links documenting this (same name) behavior -> EDIT (2017.01.24) — have a look at What If I Have a Module and a Package With The Same Name? Interestingly normally packages take precedence but apparently our launcher violates this.

EDIT (2015.01.17): I did not mention we use a custom launcher dissected here.

dukevindukevin

22k36 gold badges80 silver badges110 bronze badges

YuanhuiYuanhui

4595 silver badges15 bronze badges

Linux: Imported modules are located in /usr/local/lib/python2.7/dist-packages

If you’re using a module compiled in C, don’t forget to chmod the .so file after sudo setup.py install.

sudo chmod 755 /usr/local/lib/python2.7/dist-packages/*.so

answered May 30, 2014 at 22:50

answered Sep 4, 2013 at 2:52

answered Mar 27, 2018 at 12:41

michael-slxmichael-slx

6558 silver badges15 bronze badges

juanignaciosljuanignaciosl

3,3952 gold badges26 silver badges28 bronze badges

ioaniatrioaniatr

2774 silver badges15 bronze badges

PoliPoli

7710 bronze badges

GhotiGhoti

7374 silver badges18 bronze badges

After just suffering the same issue I found my resolution was to delete all pyc files from my project, it seems like these cached files were somehow causing this error.

Easiest way I found to do this was to navigate to my project folder in Windows explorer and searching for *.pyc, then selecting all (Ctrl+A) and deleting them (Ctrl+X).

Its possible I could have resolved my issues by just deleting the specific pyc file but I never tried this

RocketqRocketq

5,01420 gold badges75 silver badges123 bronze badges

Toivo SäwénToivo Säwén

1,6732 gold badges14 silver badges33 bronze badges

In your particular case it looks like you’re trying to import SomeObject from the myapp.py and TestCase.py scripts. From myapp.py, do

import SomeObject

since it is in the same folder. For TestCase.py, do

from ..myapp import SomeObject

However, this will work only if you are importing TestCase from the package. If you want to directly run python TestCase.py, you would have to mess with your path. This can be done within Python:

import sys
sys.path.append("..")
from myapp import SomeObject

though that is generally not recommended.

In general, if you want other people to use your Python package, you should use distutils to create a setup script. That way, anyone can install your package easily using a command like python setup.py install and it will be available everywhere on their machine. If you’re serious about the package, you could even add it to the Python Package Index, PyPI.

answered Feb 21, 2012 at 18:46

The function import looks for files into your PYTHONPATH env. variable and your local directory. So you can either put all your files in the same directory, or export the path typing into a terminal::

export PYTHONPATH="$PYTHONPATH:/path_to_myapp/myapp/myapp/"

exporting path is a good way. Another way is to add a .pth to your site-packages location.
On my mac my python keeps site-packages in /Library/Python shown below

/Library/Python/2.7/site-packages

I created a file called awesome.pth at /Library/Python/2.7/site-packages/awesome.pth and in the file put the following path that references my awesome modules

/opt/awesome/custom_python_modules

answered May 20, 2013 at 23:36

阿东刘阿东刘

1391 silver badge2 bronze badges

KrysaleadKrysalead

811 silver badge1 bronze badge

未来陆家嘴顶尖的投资人未来陆家嘴顶尖的投资人

1,71820 silver badges19 bronze badges

answered Aug 21, 2018 at 9:12

astrowalkerastrowalker

2,9852 gold badges16 silver badges36 bronze badges

let’s say i write a module

import os
my_home_dir=os.environ['HOME'] // in windows 'HOMEPATH'
file_abs_path=os.path.join(my_home_dir,"my_module.py")

with open(file_abs_path,"w") as f:
   f.write("print('I am loaded successfully')")

import importlib
importlib.util.find_spec('my_module') ==> cannot find

we have to tell python where to look for the module. we have to add our path to the sys.path

 import sys
 sys.path.append(file_abs_path)

now importlib.util.find_spec('my_module') returns:

  ModuleSpec(name='my_module', loader=<_frozen_importlib_external.SourceFileLoader object at 0x7fa40143e8e0>, origin='/Users/name/my_module.py')

we created our module, we informed python its path, now we should be able to import it

 import my_module

//I am loaded successfully

answered Sep 14, 2020 at 2:09

Deekshith AnandDeekshith Anand

1,8151 gold badge19 silver badges21 bronze badges

Mehdi BoukhechbaMehdi Boukhechba

2,4432 gold badges19 silver badges24 bronze badges

AMKAMK

4624 silver badges15 bronze badges

In your particular case it looks like you’re trying to import SomeObject from the myapp.py and TestCase.py scripts. From myapp.py, do

import SomeObject

since it is in the same folder. For TestCase.py, do

from ..myapp import SomeObject

However, this will work only if you are importing TestCase from the package. If you want to directly run python TestCase.py, you would have to mess with your path. This can be done within Python:

import sys
sys.path.append("..")
from myapp import SomeObject

though that is generally not recommended.

In general, if you want other people to use your Python package, you should use distutils to create a setup script. That way, anyone can install your package easily using a command like python setup.py install and it will be available everywhere on their machine. If you’re serious about the package, you could even add it to the Python Package Index, PyPI.

answered Feb 21, 2012 at 18:46

The function import looks for files into your PYTHONPATH env. variable and your local directory. So you can either put all your files in the same directory, or export the path typing into a terminal::

export PYTHONPATH="$PYTHONPATH:/path_to_myapp/myapp/myapp/"

exporting path is a good way. Another way is to add a .pth to your site-packages location.
On my mac my python keeps site-packages in /Library/Python shown below

/Library/Python/2.7/site-packages

I created a file called awesome.pth at /Library/Python/2.7/site-packages/awesome.pth and in the file put the following path that references my awesome modules

/opt/awesome/custom_python_modules

answered May 20, 2013 at 23:36

阿东刘阿东刘

1391 silver badge2 bronze badges

KrysaleadKrysalead

811 silver badge1 bronze badge

未来陆家嘴顶尖的投资人未来陆家嘴顶尖的投资人

1,71820 silver badges19 bronze badges

answered Aug 21, 2018 at 9:12

astrowalkerastrowalker

2,9852 gold badges16 silver badges36 bronze badges

let’s say i write a module

import os
my_home_dir=os.environ['HOME'] // in windows 'HOMEPATH'
file_abs_path=os.path.join(my_home_dir,"my_module.py")

with open(file_abs_path,"w") as f:
   f.write("print('I am loaded successfully')")

import importlib
importlib.util.find_spec('my_module') ==> cannot find

we have to tell python where to look for the module. we have to add our path to the sys.path

 import sys
 sys.path.append(file_abs_path)

now importlib.util.find_spec('my_module') returns:

  ModuleSpec(name='my_module', loader=<_frozen_importlib_external.SourceFileLoader object at 0x7fa40143e8e0>, origin='/Users/name/my_module.py')

we created our module, we informed python its path, now we should be able to import it

 import my_module

//I am loaded successfully

answered Sep 14, 2020 at 2:09

Deekshith AnandDeekshith Anand

1,8151 gold badge19 silver badges21 bronze badges

Mehdi BoukhechbaMehdi Boukhechba

2,4432 gold badges19 silver badges24 bronze badges

AMKAMK

4624 silver badges15 bronze badges