The Deck class isn't being found because it isn't in your current name space. To use it, you need to refer to it using the module name. You'll have the same problem with the test2 function. Change war.py to look like this:

import deck

d = deck.Deck()
deck.test2()
d.test()

Another error you will encounter is that your Deck.test method doesn't expect any parameters, but needs to. Add "self" (without quotes) between the parentheses.

You have mutual top-level imports, which is almost always a bad idea.

If you really must have mutual imports in Python, the way to do it is to import them within a function:

# In b.py:
def cause_a_to_do_something():
    import a
    a.do_something()

Now a.py can safely do import b without causing problems.

(At first glance it might appear that cause_a_to_do_something() would be hugely inefficient because it does an import every time you call it, but in fact the import work only gets done the first time. The second and subsequent times you import a module, it's a quick operation.)

Hi @chrislarge305, I can confirm that, as @alcampopiano suspected, the issue is a circular import, which Python doesn’t like! You’re importing AddMeasurementComponent from navigation, and you’re importing navigation from AddMeasurementComponent. One way to solve this problem is to import the navig…

When you import lib, you're importing the package. The only file to get evaluated and run in this case is the 0 byte __init__.py in the lib directory.

If you want access to your function, you can do something like this from lib.mod1 import mod1 and then run the mod12 function like so mod1.mod12().

If you want to be able to access mod1 when you import lib, you need to put an import mod1 inside the __init__.py file inside the lib directory.

The problem is submodules are not automatically imported. You have to explicitly import the api module:

import myproject.mymodule.api
print myproject.mymodule.api.MyClass

If you really insist on api being available when importing myproject.mymodule you can put this in myproject/mymodule/__init__.py:

import myproject.mymodule.api

Then this will work as expected:

from myproject import mymodule

print mymodule.api.MyClass 

Do you think you could maybe explain why the two functions shouldn't be in the Player class? · It's a matter of class design. Normally, functions in a class Player execute player's action or report about player's state, or they may execute code relative to all players (in this case they are class methods or static methods). Technically, one says that each class has a certain number of "responsibilities". General utility functions like ask_yes_or_no() are unrelated to this class. · If you absolutely want to have this functions in the class, write · @staticmethod · def ask_yes_or_no(): # no self parameter · ... · and then use game.Player.ask_yes_or_no()

In your A.py, use from Hasher import V2
Basically, when you are just importing 'Hasher' only the init.py file gets loaded.
Reference: Python error: AttributeError: 'module' object has no attribute

Note: In your Hasher/__init__.py file, if you import V2 using from . import V2, then you can use it by directly calling Hasher.V2 from A.py

The thing with imports is they are relative to the "working directory". And that directory is decided by the IDE (vscode). It could be a directory that you don't expect, and it could be loading something else instead of what you want. So do 3 things to check what goes wrong. 1 - Add code to the start of converters.py to make sure it gets loaded, and print its path print("converters is loaded") print(__file__) def lbstokg(...): ... ... 2 - Add code to the start of main, to figure out the current working directory, and list files there. import os print(os.getcwd()) print(os.listdir()) 3 - add code in main to print converter's file. import converters print(converters.__file__) this should help find any issues, if you can't figure out what's wrong, show us the output of these additions.

This may not be the cause for everyone, but I've identified at least one set of triggers.

1. Run Python toolbox tool from ArcCatalog
2. Geoprocessing history is on and includes a result from #1.
3. When starting a new ArcCatalog session, no geoprocessing windows are open initially (such as ArcToolbox window, Python window, Results window).

If the above are all true, the Python toolbox tool will show the AttributeError: 'module' object has no attribute 'Parameter' exception.

Clearing out the history (or not logging it at all) will avoid the issue, probably why I didn't see this before as I rarely retain my history.

Right-clicking on the toolbox and using refresh will clear the error, but it will come up again in the future as long as the list above remains true. However, if the tool is importing the tool class from a separate tool file (like the case above) a refresh will not be enough. For that, I had to force it by including a reload in the .pyt, and then a refresh on the toolbox will clear the error.

# Using example of toolbox.pyt above
import toolpackage.configurator  # add import
reload(toolpackage.configurator)  # add a forced reload
from toolpackage.configurator import ToolboxConfigurator