-
Notifications
You must be signed in to change notification settings - Fork 183
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
colap ,pip install zigzag #42
Comments
I created a fork that works: copy all and paste in a cell (copy also the dot at the end of !pip install and the dot dot at the end of %cd) : !git clone https://github.com/ambroseikpele/ZigZag |
Thanks so much Ambrose! Really awesome work! |
Thanks so much |
@ambroseikpele |
What do you mean "copy all and paste in a cell", I don't understand what you mean, where in which cell ? |
@AureliusMarcusHu He means to run the following code within a jupyter notebook cell.
|
After installing I run into a dtype mismatch error:
I have two computers: The first one have the original zigzag package installed 3 years ago without zigzag installing error. The second one has the zigzag fork package installed, because the install error of the original zigzag package. There must be some difference in the zigzag package. Please help me, I need this package working. |
@AureliusMarcusHu I have solved this in my fork, i just created a pull request to Ambrose's repo: Its really simple to fix, just see my changes in the commit i linked. |
@amirzamli Pull Request merged |
@amirzamli I made the changes manually in core.pyx, but I have still the same error. |
Thanks to all of you, I'm very happy now ... :) |
error
Collecting zigzag
Using cached zigzag-0.3.2.tar.gz (112 kB)
error: invalid-pyproject-build-system-requires
× Can not process zigzag from https://files.pythonhosted.org/packages/d4/88/028c3d29b17cd2d4cfcc2305bc42e0363d64451e3eda880aab1d0e579069/zigzag-0.3.2.tar.gz
╰─> This package has an invalid
build-system.requires
key in pyproject.toml.It contains an invalid requirement: 'Cython>=^0.29'
note: This is an issue with the package mentioned above, not pip.
hint: See PEP 518 for the detailed specification.
The text was updated successfully, but these errors were encountered: