alibaba / pemja

Apache License 2.0
90 stars 25 forks source link

python setup.py egg_info failed #7

Closed a49a closed 2 years ago

a49a commented 2 years ago
python setup.py egg_info

The following is error message

numpy not found
python -m pip install -r flink-python/dev/dev-requirements.txt

The following is error message

Looking in indexes: https://pypi.tuna.tsinghua.edu.cn/simple
Collecting pemja==0.1.5
  Using cached https://pypi.tuna.tsinghua.edu.cn/packages/36/32/18615e64be80b70c4c95dc2d7d3b20a9d706dc5fcefc92ebafe0348ca3dc/pemja-0.1.5.tar.gz (32 kB)
  Preparing metadata (setup.py) ... error
  error: subprocess-exited-with-error

  × python setup.py egg_info did not run successfully.
  │ exit code: 255
  ╰─> [1 lines of output]
      numpy not found
      [end of output]

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

× Encountered error while generating package metadata.
╰─> See above for output.

note: This is an issue with the package mentioned above, not pip.
hint: See above for details.
kphan102 commented 2 years ago

I also have the same issue on M1 chip. Any solution or work around?

HuangXingBo commented 2 years ago

I haven't tested installation in M1 chip. Do you mean there will be errors installing on the M1?

HuangXingBo commented 2 years ago

We need to release mac-arm wheel package to support M1. Currently, the work around is install numpy firstly, and then install pemja.

a49a commented 2 years ago

I will fix this.

kphan102 commented 2 years ago

We need to release mac-arm wheel package to support M1. Currently, the work around is install numpy firstly, and then install pemja.

I installed numpy==1.21.4 first but I ran into the setup.py issue as mentioned here. I would be able to provide testing for the M1 installation since I want to build flink docker using native architecture.

kphan102 commented 2 years ago

Any progress so far for this issue ?

HuangXingBo commented 2 years ago

Any progress so far for this issue ?

@kphan102 I'm working on this. It is expected to be resolved today or tomorrow.

HuangXingBo commented 2 years ago

I have uploaded pemja m1 wheels to https://pypi.org/project/pemja/#files

kphan102 commented 2 years ago

I have uploaded pemja m1 wheels to https://pypi.org/project/pemja/#files

Thnks alot for this. Let me try to test out on my m1

kphan102 commented 2 years ago

everything works with the M1. Thanks alot @HuangXingBo However I found a small issue with flink-python, where should I report the issue in the flink repo?

HuangXingBo commented 2 years ago

@kphan102 Thanks for the test. Is the issue you said about installation of pyflink in M1?

HuangXingBo commented 2 years ago

The wheel package on PyFlink's M1 is indeed not yet available. There may be problems with the installation. You can create an issue in flink community. I will solve this in flink release-1.16.

kphan102 commented 2 years ago

@HuangXingBo ah, the issue is related to one of the common instant variable. DEFAULT_OUTPUT_TAG, I built and run 1.16-snapshot on M1 ( i'm still using old apache-flink-libraries v1.15) but when I submit the job, I always got KeyError. When I updated that variable to DEFAULT_OUTPUT_TAG= "output" then the issue seems temporarily resolved. I was wondering if I can report this issue on the flink community?

HuangXingBo commented 2 years ago

@kphan102 You need to ensure the versions of apache-flink-libraries and apache-flink same. Your problem has nothing to do with M1