Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Installing smop #124

Open
andreeaf13 opened this issue May 30, 2018 · 5 comments
Open

Installing smop #124

andreeaf13 opened this issue May 30, 2018 · 5 comments

Comments

@andreeaf13
Copy link

Hi,
I'm new to Python, Github and i have some questions regarding the installation. Can I install this tool on windows 10? And how to proceed? I tried anything, but unfortunately not worked.

@victorlei
Copy link
Owner

Try to install anaconda first. Once done, install smop with pip

If you cut/paste error messages it will make possible to say something more specific

@RobBW
Copy link

RobBW commented Jun 5, 2018 via email

@victorlei
Copy link
Owner

Rob

Regarding versioning problem: my guess is that you have an old version of smop installed ssomewheere in your path. Try

find / -name smop -print 2> /dev/null

Get rid of old versions and reinstall with pip

Regarding the other bugs take a look at http://chiselapp.com/user/victorlei/repository/smop-dev/rptview?rn=1

As you see there are lots of probleems there
Victor

@victorlei
Copy link
Owner

Rob,

I really appreciate your effort to debug the versioning scheme. Here is how it works today --- it's entirely possible I overlooked something.

The versioning is managed in two files: setup.py and smop/version.py. Every time you run setup.py it goes to git and asks for the latest annotated version. Presumably, you have git installation working. Once git reports with something like "0.40-deadbeef" , setup.py overwrites version.py with the reported version. All this happens during the installation phase, every timie setup.py is run.

When smop is used, it imports version.py and loads version variable from version.py.
That's the whole story. Do I miss something? The scheme is not foolproof. For example, having several smop installations living side by side on the same system is a proven road to hell.

Victor

@hidetokoizumi
Copy link

At #123 , you kindly suggested to install smop with pip, and check the version by 'smop --version', but I got the following output:

Hidetos-MacBook-Air:~ hidetokoizumi$ pip install smop
Collecting smop
Requirement already satisfied: numpy in ./anaconda3/lib/python3.6/site-packages (from smop) (1.14.0)
Requirement already satisfied: scipy in ./anaconda3/lib/python3.6/site-packages (from smop) (1.0.0)
Requirement already satisfied: networkx in ./anaconda3/lib/python3.6/site-packages (from smop) (2.1)
Requirement already satisfied: ply in ./anaconda3/lib/python3.6/site-packages (from smop) (3.10)
Requirement already satisfied: decorator>=4.1.0 in ./anaconda3/lib/python3.6/site-packages (from networkx->smop) (4.2.1)
Installing collected packages: smop
Successfully installed smop-0.0.0

Hidetos-MacBook-Air:~ hidetokoizumi$ smop --version
Traceback (most recent call last):
File "/Users/hidetokoizumi/anaconda3/bin/smop", line 7, in
from smop.main import main
File "/Users/hidetokoizumi/anaconda3/lib/python3.6/site-packages/smop/init.py", line 4, in
import version
ModuleNotFoundError: No module named 'version'

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants