Skip to content

c-VEP Speller installing issue in timeflux_hackeeg for Windows #13

Description

@vicmarcag

Hey!

It seems that timeflux_hackeeg requires gnureadline, which is not available in Windows OS. Maybe pyreadline3 would be a solution.

Is there any workaround?

Collecting timeflux_hackeeg
Using cached timeflux_hackeeg-0.3.1-py3-none-any.whl.metadata (1.5 kB)
Requirement already satisfied: timeflux>=0.6.1 in c:\users\victor\documents\softwareprojects\timeflux\venv\lib\site-packages (from timeflux_hackeeg) (0.17.1)
Collecting hackeeg>=0.2.0 (from timeflux_hackeeg)
Using cached hackeeg-0.3.0-py3-none-any.whl.metadata (4.1 kB)
Collecting pyserial (from hackeeg>=0.2.0->timeflux_hackeeg)
Using cached pyserial-3.5-py2.py3-none-any.whl.metadata (1.6 kB)
Collecting bitstring (from hackeeg>=0.2.0->timeflux_hackeeg)
Using cached bitstring-4.2.3-py3-none-any.whl.metadata (5.0 kB)
Requirement already satisfied: numpy in c:\users\victor\documents\softwareprojects\timeflux\venv\lib\site-packages (from hackeeg>=0.2.0->timeflux_hackeeg) (1.26.4)
Collecting jsonlines (from hackeeg>=0.2.0->timeflux_hackeeg)
Using cached jsonlines-4.0.0-py3-none-any.whl.metadata (1.6 kB)
Requirement already satisfied: msgpack in c:\users\victor\documents\softwareprojects\timeflux\venv\lib\site-packages (from hackeeg>=0.2.0->timeflux_hackeeg) (1.1.0)
Collecting autopep8 (from hackeeg>=0.2.0->timeflux_hackeeg)
Using cached autopep8-2.3.1-py2.py3-none-any.whl.metadata (16 kB)
Collecting gnureadline (from hackeeg>=0.2.0->timeflux_hackeeg)
Using cached gnureadline-8.2.10.tar.gz (3.2 MB)
Installing build dependencies ... done
Getting requirements to build wheel ... error
error: subprocess-exited-with-error

× Getting requirements to build wheel did not run successfully.
│ exit code: 1
╰─> [1 lines of output]
Error: this module is not meant to work on Windows (try pyreadline3 instead)
[end of output]

note: This error originates from a subprocess, and is likely not a problem with pip.
error: subprocess-exited-with-error

× Getting requirements to build wheel did not run successfully.
│ exit code: 1
╰─> See above for output.

note: This error originates from a subprocess, and is likely not a problem with pip.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions