Compatibility with Python 3.12, ModuleNotFoundError: No module named 'imp' #153
Comments
dtorres-sf
added a commit
to surefyresystems/actions-aws-eb
that referenced
this issue
Oct 22, 2023
To workaround the update to 3.12 causing issues with EB: aws/aws-elastic-beanstalk-cli-setup#153
|
I'm encountering this issue as well. I tried to run "eb version" and was prompted this error |
|
Got this error on the last version of Fedora |
|
Just posting so I can be alerted when a fix for this issue is posted. |
|
Same issue here 👋 |
|
same. |
|
already solved!, just downgrade your python with version Python 3.11.7 and Pip version pip 23.2.1 |
|
Same. Downgrading Python to 3.11 to fix this, but would be nice if this was addressed in the repo |
|
if you are using windows 11 and python 3.12, check ~\dev on ⛅ (Seoul)
PS > get-command py
CommandType Name Version Source
----------- ---- ------- ------
Application py.exe 3.12.2150… C:\Users\hdformat\AppData\Local\Programs…check pythons on your system ~\dev on ⛅ (Seoul)
PS > py --list
-V:3.12 * Python 3.12 (64-bit)install python 3.11 from dowloading a installer on python official site check pythons again after ~\dev on ⛅ (Seoul)
PS > py --list
-V:3.12 * Python 3.12 (64-bit)
-V:3.11 Python 3.11 (64-bit)run eb-cli installer using python 3.11 ~\dev on ⛅ (Seoul) took 3s
PS > py -3.11 .\aws-elastic-beanstalk-cli-setup\scripts\ebcli_installer.py
***********************************
1. Locating virtualenv installation
***********************************
...
***************
6. Finishing up
***************
Success!
EBCLI has been installed.run eb cli ~\dev on ⛅ (Seoul) took 10s
PS > eb --help
usage: eb (sub-commands ...) [options ...] {arguments ...}
Welcome to the Elastic Beanstalk Command Line Interface (EB CLI).
For more information on a specific command, type "eb {cmd} --help".
commands:
abort Cancels an environment update or deployment.
appversion Listing and managing application versions
clone Clones an environment.
codesource Configures the code source for the EB CLI to use by default.
config Modify an environment's configuration. Use subcommands to manage saved configurations.
console Opens the environment in the AWS Elastic Beanstalk Management Console.
create Creates a new environment.
deploy Deploys your source code to the environment.
events Gets recent events.
health Shows detailed environment health.
init Initializes your directory with the EB CLI. Creates the application.
labs Extra experimental commands.
list Lists all environments.
local Runs commands on your local machine.
logs Gets recent logs.
open Opens the application URL in a browser.
platform Commands for managing platforms.
printenv Shows the environment variables.
restore Restores a terminated environment.
scale Changes the number of running instances.
setenv Sets environment variables.
ssh Opens the SSH client to connect to an instance.
status Gets environment information and status.
swap Swaps two environment CNAMEs with each other.
tags Allows adding, deleting, updating, and listing of environment tags.
terminate Terminates the environment.
upgrade Updates the environment to the most recent platform version.
use Sets default environment.
options:
-h, --help show this help message and exit
--debug toggle debug output
--quiet suppress all output
-v, --verbose toggle verbose output
--profile PROFILE use a specific profile from your credential file
-r REGION, --region REGION
use a specific region
--no-verify-ssl don't verify AWS SSL certificates
--version show application/version info
To get started type "eb init". Then type "eb create" and "eb open"
|
|
I don't get this - i thought the whole point of using python virtual environments is that you could specify a version of python to use. Why is it necessary to downgrade python when your installer is using a virtual environment to begin with? I can't deploy my website right now because the person who set it up, created the deploy script using this ebcli tool and the tool won't work on a newly upgraded machine because of this 'imp' package. |
|
aaaaaaaaaaaaaaaaaaaand installing with python 3.11 doesn't work. I #$%#$^ hate python |
|
Just ran into this myself -- can't believe this has been open for this long. Switched from having in installed in my python project's venv to this because of the dependency issues with botocore. Kind of hilarious that this is the official way to install the tool and it doesn't work either. I also really don't understand why I have to mess around with installing virtualenv... Why not just run it with a regular venv which is native to python and cut out that extra step? |
|
At the very least this repo's readme needs to be updated to clarify that python 3.12+ should NOT be used. This shouldn't take too long... |
|
Hi! |
|
Running These are the steps I followed to get it working on macOS:
|
|
up up up |
|
This is still a problem. |
|
would be nice to get this fixed |
|
Just ran into this. Devs., please update things so that it works on Python 3.12. The latest Ubuntu installs Python 3.12 |
|
It would be nice to get a fix for this. |
|
This is fixed now. EB CLI >= 3.21.0 works with Python 3.12 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
eb tool broken after upgrade to python 3.12 due to imp module remotion (python/cpython#98040)
Stacktrace:
The text was updated successfully, but these errors were encountered: