Re: venv --upgrade 3.12.0rc2 --> 3.12.0rc3 failure
> On 27 Sep 2023, at 12:50, Robin Becker via Python-list > wrote: > > Attempting venv upgrade 3.12.0rc2 --> 3.12.0rc3 I find pyvenv.cfg changes, > but the virtual python doesn't. > I guess this ought to be a bug. You must delete and then recreate the venv if the version of python changes. It is not a bug in python. Barry -- https://mail.python.org/mailman/listinfo/python-list
Re: venv --upgrade 3.12.0rc2 --> 3.12.0rc3 failure
On 28/09/2023 10:05, Barry via Python-list wrote: So this must be the source of my confusion user@host:~ $ python312 -mvenv --help .. --upgrade Upgrade the environment directory to use this version of Python, assuming Python has been upgraded in-place. .. I have a different version, but it's not 'in place'. thanks -- Robin On 27 Sep 2023, at 12:50, Robin Becker via Python-list wrote: Attempting venv upgrade 3.12.0rc2 --> 3.12.0rc3 I find pyvenv.cfg changes, but the virtual python doesn't. I guess this ought to be a bug. You must delete and then recreate the venv if the version of python changes. It is not a bug in python. Barry -- https://mail.python.org/mailman/listinfo/python-list
Installing package as root to a system directory
Hi, I use poetry to develop system software packages as a normal user. To install the packages I use, again as a normal user export PYTHONUSERBASE=/some/path pip3 install --user somepackage.whl and add /some/path to /usr/lib64/python3.6/site-packages/zedat.pth This works well enough, but seems to me to be a little clunky, mainly because the files don't then belong to root. The most correct way, in my case, would probably be to create an RPM out of the Python package, but that seems like it would be too much overhead. What other approaches to people use? Cheers, Loris -- This signature is currently under constuction. -- https://mail.python.org/mailman/listinfo/python-list
Re: upgrade of pip on my python 2.7 version
On Wednesday, 27 September 2023 at 23:33:02 UTC+2, Chris Angelico wrote: > On Thu, 28 Sept 2023 at 07:27, Mats Wichmann via Python-list > wrote: > > > > Upgrading to Python 3 is the best answer... except when it isn't. If > > you want to convert a small project it's usually not too hard; and using > > a conversion tool can work well. > Just remember that Python 2.7.18, the very last version of Python 2, > was released in 2020 and has not changed since. There are not even > security patches being released (at least, not from python.org - but > if you're using a different distribution of Python, you are also quite > possibly using their package manager rather than pip). Staying on a > version of Python that hasn't had new features since 2010 and hasn't > had bug fixes since 2020 is going to become increasingly problematic. > > Convert your code. Pay the price in development time now and then reap > the benefits, rather than paying the price when you run into a massive > issue somewhere down the track and there's no options left to you. > > Convert while you still have the luxury of running the old code. > > ChrisA but how do i convert it chris just downloading the python version 3 will solve my issue? and what about the changes -- https://mail.python.org/mailman/listinfo/python-list
Re: upgrade of pip on my python 2.7 version
On 9/28/2023 9:23 AM, Zuri Shaddai Kuchipudi via Python-list wrote: On Wednesday, 27 September 2023 at 23:33:02 UTC+2, Chris Angelico wrote: On Thu, 28 Sept 2023 at 07:27, Mats Wichmann via Python-list wrote: Upgrading to Python 3 is the best answer... except when it isn't. If you want to convert a small project it's usually not too hard; and using a conversion tool can work well. Just remember that Python 2.7.18, the very last version of Python 2, was released in 2020 and has not changed since. There are not even security patches being released (at least, not from python.org - but if you're using a different distribution of Python, you are also quite possibly using their package manager rather than pip). Staying on a version of Python that hasn't had new features since 2010 and hasn't had bug fixes since 2020 is going to become increasingly problematic. Convert your code. Pay the price in development time now and then reap the benefits, rather than paying the price when you run into a massive issue somewhere down the track and there's no options left to you. Convert while you still have the luxury of running the old code. ChrisA but how do i convert it chris just downloading the python version 3 will solve my issue? and what about the changes You have to modify your existing Python code. It's often easy to do. There is the tool that tries to convert from Python 2 to Python 3; you may need to do some extra work after that. Depending on the code you may even be able to make it work with both Python 2.7 and 3.x. Often the biggest change is to print statements: Python 2: print a, b, c Python3: print(a, b, c) If you are very unlucky, your code will depend on some package that has never been ported to Python 3. But that would be unusual. -- https://mail.python.org/mailman/listinfo/python-list
