I’m trying to create an AWS Lambda Deployment Package, so I can use it as an AWS Lambda Layer. Specifically, I’m trying to use the ipopt sovler, in conjuction with the pyomo and cython. I can get the pyomo packaged without issue, but when I try to pip install ipopt for the package I get an error: I am trying
Tag: virtualenv
How to set PIPENV_VENV_IN_PROJECT on per-project basis
I want pipenv to create its virtualenv in $PROJECTDIR/.venv automatically for everyone who checks out the project. So far, I see only the following options working, none of which is satisfying: Ask users to set PIPENV_VENV_IN_PROJECT=1 globally, forcing my project preferences on each of their other projects. Ask users to always invoke pipenv via “PIPENV_VENV_IN_PROJECT=1 pipenv” when inside my project,
pip command not found in virtual env even if file is there
These are the steps I did: Created a virtual env using python3 -m venv myvenv Activate the virtual env using myvenv/bin/activate Run python -m pip install –upgrade pip, to upgrade pip. run pip install -r requirements.txt It throws an error: bash: /Users/vince/Django Projects/test/myvenv/bin/pip: “/Users/vince/Django: bad interpreter: No such file or directory When I tried using pip2 install, it works, why
Python produces: OSError: [WinError 193] %1 is not a valid Win32 application, but only with activate_this.py
This is presumably the same as Python produces: OSError: [WinError 193] %1 is not a valid Win32 application However, that has no answers, and I have additional details for my situation. Background: I’m using a venv, it gets activated internally with activate_this.py via: This worked on python2 at least… when I import numpy I get: If I activate the venv
How to install dependencies from a copied pipfile inside a virtual environment?
The problem originates when I start by cloning a git project that uses pipenv, so it has a Pipfile + Pipfile.lock. I want to use a virtual environment with the project so I run pipenv shell. I now have a virtual environment created and I am inside the virtual environment. The project obviously has a lot of dependencies (listed in
how can I find the path of virtualenv python
how can I find the path of virtualenv python ,built with this tutorial? (i want to find python in this env and use it in my eclipse) Answer You can use which to find out which binary will be executed… For example: By default it just shows the first match, but you can give the -a argument to show all:
PyCharm 2018 Python Unresolved Reference ‘django’ VirtualEnv
I have the newest PyCharm version (2018) and the latest Django version (2.1) and Python (3.6) When I want to import something in PyCharm from Django: I get an error message under django stating: Unresolved reference ‘django’ I created a virtual environment and I ran a project on it, the most famous one (polls) and it ran very well. But
How can I create the minimum size executable with pyinstaller?
I am on Windows 10, I have anaconda installed but I want to create an executable independently in a new, clean minimal environment using python 3.5. So I did some tests: TEST1: I created a python script test1.py in the folder testenv with only: Then I created the environment, installed pyinstaller and created the executable And it creates my test1.exe
Separating development and production dependencies with virtualenv
I have a simple flask app, where I use virtualenv for managing my dependencies. However, I would like to separate my dependencies. For testing I use Flask-Testing, but this is a dependency I wouldn’t want to include in my production environment. How can separate my dependencies, so that I have separate dependencies for development and for production? Answer You can
Failed to activate virtualenv with pyenv
I run: And I get: I am trying to follow this tutorial: https://tutorials.technology/tutorials/59-Start-a-flask-project-from-zero-building-api-rest.html Other info: I recently made my .bash_profile it contains: What should I do to properly start virtualenv? Answer That should be in .bashrc, not .bash_profile. The latter is executed only by login shells, the former by all interactive shells.