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
SyntaxError: future feature annotations is not defined #14
Comments
Two solutions:
|
Thx for your reply. it works! |
excuse me i was countered this error and tried the solution but error exists . but i have this
instead of site-packages Appreciate your help |
I am using reels downloader with flask framework and works well on localhost but not on deployed site, and getting error as future feature annotations is not defined (profile.py, line 1) |
csuhan/ReDet#14 (comment) future feature annotations is not defined (profile.py, line 1)
Finally I found solution, |
Minimal RHEL and CentOS 7 images have fallen out of date quite quickly and have many dependencies which may be updated with installed ansible related packages. Do a "yum update" first with clean new golden images, to avoid the bulky accumulation of such updates for breaking other installations. Changing your default python 3 is not a step for the weak of heart. RHEL 8 and CentOS 8 have python3.8 available, but it's not published or not yet published for RHEL 7, which is its own problem. It is published as an SCL component, but those are notoriously pesky to work with and are not supported by EPEL unlike the way python3.6 was supported for a time. It's very frustrating that Red Hat elected to publish python36 packages as python3, it has seriously broken compatibility with various EPEL modules and with Amazon Linux 2, which followed Red Hat's ill-thought-out behaviour and published python3.7 packages as "python3", leading to thorough brokenness with EPEL, especially for current ansible-core releases. |
Doesn't work for me :( |
1 similar comment
Doesn't work for me :( |
For my purposes, this is how I'm installing newer python versions on centos 7. Best to do in a base image of some kind, as it's very slow.
If you don't need libpython, you can simplify a little, but figured I'd leave some breadcrumbs for y'all |
Doesn't work with airflow packages with option 2 (```
|
try "pip3 install scipy" |
The default python and pip on RHEL 7 are python 2.7 Installing python 3 is
an extra step, "yum install python3 python3-pip"
The attempts to deduce and outsmart the default pythons has been an ongoing
issue for ansible. It's much simpler to consistently use "pyp3" or
"python3" instead of "pytho" in all the scripts: it's what I do for the RPM
building tools I publish for ansible and ansible-core.
The frequency of published directives to do "pip install" as the root user
are their own distinct but related problem, encouraging the out-of-band and
unmanaged installation of incompatible dependency trees in the root
owned python modules. There are RPMs available for python3-scipy, and they
should be used instead if possible.
sudo yum install python3-scipy -y
Nico Kadel-Garcia
…On Fri, Nov 25, 2022 at 5:59 AM JackThird ***@***.***> wrote:
Doesn't work with airflow packages with option 2 (``` git clone -b
legacy_py3.6 https://github.com/QUVA-Lab/e2cnn.git cd e2cnn python
setup.py install
Searching for scipy
Reading https://pypi.org/simple/scipy/
Downloading https://files.pythonhosted.org/packages/0a/2e/44795c6398e24e45fa0bb61c3e98de1cfea567b1b51efd3751e2f7ff9720/scipy-1.9.3.tar.gz#sha256=fbc5c05c85c1a02be77b1ff591087c83bc44579c6d2bd9fb798bb64ea5e1a027
Best match: scipy 1.9.3
Processing scipy-1.9.3.tar.gz
Writing /var/folders/f_/7vstf97j517b5sb77v46rwq40000gq/T/easy_install-59kswnu6/scipy-1.9.3/setup.cfg
Running scipy-1.9.3/setup.py -q bdist_egg --dist-dir /var/folders/f_/7vstf97j517b5sb77v46rwq40000gq/T/easy_install-59kswnu6/scipy-1.9.3/egg-dist-tmp-jl9ck5kb
Traceback (most recent call last):
File "/usr/local/anaconda3/envs/airflowenv/lib/python3.6/site-packages/setuptools/sandbox.py", line 156, in save_modules
yield saved
File "/usr/local/anaconda3/envs/airflowenv/lib/python3.6/site-packages/setuptools/sandbox.py", line 198, in setup_context
yield
File "/usr/local/anaconda3/envs/airflowenv/lib/python3.6/site-packages/setuptools/sandbox.py", line 259, in run_setup
_execfile(setup_script, ns)
File "/usr/local/anaconda3/envs/airflowenv/lib/python3.6/site-packages/setuptools/sandbox.py", line 46, in _execfile
exec(code, globals, locals)
File "/var/folders/f_/7vstf97j517b5sb77v46rwq40000gq/T/easy_install-59kswnu6/scipy-1.9.3/setup.py", line 33, in <module>
keywords=[
RuntimeError: Python version >= 3.8 required.
try "pip3 install scipy"
—
Reply to this email directly, view it on GitHub
<#14 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAKREG7FZ6WFN444HDTULW3WKCL2TANCNFSM42P5IYQA>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
installing previous version of telegram api helped me I had problem deploying telebot on server that have only Python 3.6.9 and all these methods didnt help me |
If you need a more recent python, use one. On RHEL 7, python311 and python311-pip are easily available via RPM and you can then use "pip3.11" if needed. They were added since I previoosly wrote about SCLO releases. |
I cannot figure out how to get a working installation of the latest multiqc. I've tried installing it with multiple version of python >=3.7, but mambe keeps telling me:
Could someone provide the conda/mamba command that will create an environment with a versiuon that won't produce the error:
|
|
Hi, csuhan.
when I tested the code, an error occurred.
Traceback (most recent call last):
File "tools/test.py", line 12, in
from mmdet.apis import init_dist
File "/root/code/remote-sensing-detection/ReDet-master/mmdet/apis/init.py", line 2, in
from .train import train_detector
File "/root/code/remote-sensing-detection/ReDet-master/mmdet/apis/train.py", line 14, in
from mmdet.models import RPN
File "/root/code/remote-sensing-detection/ReDet-master/mmdet/models/init.py", line 1, in
from .backbones import * # noqa: F401,F403
File "/root/code/remote-sensing-detection/ReDet-master/mmdet/models/backbones/init.py", line 2, in
from .re_resnet import ReResNet
File "/root/code/remote-sensing-detection/ReDet-master/mmdet/models/backbones/re_resnet.py", line 5, in
import e2cnn.nn as enn
File "/usr/local/anaconda3/envs/pytorch1.4+10.1/lib/python3.6/site-packages/e2cnn-0.1.7-py3.6.egg/e2cnn/init.py", line 17, in
from e2cnn import group
File "/usr/local/anaconda3/envs/pytorch1.4+10.1/lib/python3.6/site-packages/e2cnn-0.1.7-py3.6.egg/e2cnn/group/init.py", line 4, in
from .group import Group
File "/usr/local/anaconda3/envs/pytorch1.4+10.1/lib/python3.6/site-packages/e2cnn-0.1.7-py3.6.egg/e2cnn/group/group.py", line 2
from future import annotations
^
SyntaxError: future feature annotations is not defined
how can I solve this error?
The text was updated successfully, but these errors were encountered: