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

ModuleNotFoundError: No module named 'src.scalecast' #16

Closed
callmegar opened this issue Oct 18, 2022 · 7 comments
Closed

ModuleNotFoundError: No module named 'src.scalecast' #16

callmegar opened this issue Oct 18, 2022 · 7 comments
Assignees
Labels
bug Something isn't working

Comments

@callmegar
Copy link

Failing to install on intel macOS Monterey 12.6.
Python 3.10.7
pip 22.2.2

Tried multiple versions (latest, 0.14.7, 0.13.11 all produce the same results:

Collecting scalecast
Using cached SCALECAST-0.15.1.tar.gz (403 kB)
Preparing metadata (setup.py) ... error
error: subprocess-exited-with-error

× python setup.py egg_info did not run successfully.
│ exit code: 1
╰─> [6 lines of output]
Traceback (most recent call last):
File "", line 2, in
File "", line 34, in
File "/private/var/folders/0f/m_0sfrcn7c56zl0026b1k62c0000gq/T/pip-install-k0tc2z79/scalecast_d8f7a8ae59984787adfbedc8a557540a/setup.py", line 4, in
from src.scalecast.init import version as version
ModuleNotFoundError: No module named 'src.scalecast'
[end of output]

@mikekeith52 mikekeith52 self-assigned this Oct 18, 2022
@mikekeith52 mikekeith52 added the bug Something isn't working label Oct 18, 2022
@mikekeith52
Copy link
Owner

I tested installation for Python 3.10.7 pip 22.2.2 and could not replicate the error. I also have it installed successfully on my macOS Montery 12.6. Are you using pip install scalecast to install?

The only idea I have would be to clear out pip's cache and try again. Maybe this resource can help: https://www.janbasktraining.com/community/python-python/removing-pips-cache#:~:text=If%20you%20want%20to%20force,help%20you%20clear%20pip%20cache

@callmegar
Copy link
Author

Thanks for checking, I tried the --no-cache-dir but got the same results, this is my pip location
/Library/Frameworks/Python.framework/Versions/3.10/bin/pip3
is it the same as yours, thinking it might have something to do with the paths

@mikekeith52
Copy link
Owner

Looks like mine is in C:\Users\michaelkeith\AppData\Local\Programs\Python\Python310\Scripts so that may be it. I don't know enough about pip to understand why the different locations would cause the installation to fail. I could take the line that is causing the failure out of my next distribution update and start entering in that info manually in setup.py every time I make an update. Is that something you'd like to have happen?

@callmegar
Copy link
Author

Yes, that would be great.

mikekeith52 pushed a commit that referenced this issue Oct 19, 2022
- added the `util.find_optimal_transformation()` function.
- changed setup.py so that version needs to be added manually to make an update (#16).
- `Forecaster.integrate()` now has `**kwargs` that are passed to `Forecaster.adf_test()`.
- changed some data processing in `SeriesTransform.DiffRevert()` to accomodate a future change from pandas.
- changed the name of `util.find_series_transformation()` to `util.find_statistical_transformation()`. this function is new as of 0.15.0 so hopefully it has not been adopted widely yet and this change doesn't cause issues for users.
- added a try/except wrapper around the `self.f.typ_set()` code in `SeriesTransformer.DetrendTransform()`
- drops null values before running though `Forecaster.normality_test()`.
- changed the import in `util` to `from scalecast import Pipeline` as the `util.find_series_transformation()` was not working because of it.
@mikekeith52
Copy link
Owner

I just uploaded 0.15.2. Please try installing this version and let me know if it does or doesn't work.

@callmegar
Copy link
Author

It worked! straight on the MacOS global install, thank you. I also tried installing 0.15.1 on a pipenv virtual environment and it also worked Ok. So it seems like it was a an issue with the paths on the MacOS

@mikekeith52
Copy link
Owner

Great news! Closing the issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants