Re: Need a Python 3.8 virtual environment
Thank you so much to the many folks on debian-python who responded with instructions and pointers! On Wednesday, March 3, 2021 4:45:46 A.M. CST Julien Palard wrote: > As other told, the right way is probably to compile it yourself (or use > pyenv, but I don't like pyenv "shims", I prefer to keep it simple). Thank you for the detailed instructions! I used this method to build python myself and now I have the virtual environment set up. Regards, -Steve signature.asc Description: This is a digitally signed message part.
Re: How can I override module name in autopkgtest-pkg-python
On Wed, Mar 3, 2021 at 8:12 PM Andreas Tille wrote: > I worked on the package python-cython-blis[1] FYI, upstream is very hostile towards having their software in Debian so I suggest you cease packaging this and anything that depends on it: https://github.com/explosion/cython-blis/issues/32 The developers reference mentions that packaging software with hostile upstream developers is often not a good idea. https://www.debian.org/doc/manuals/developers-reference/developer-duties.en.html#coordination-with-upstream-developers "If you find that the upstream developers are or become hostile towards Debian or the free software community, you may want to re-consider the need to include the software in Debian. Sometimes the social cost to the Debian community is not worth the benefits the software may bring." -- bye, pabs https://wiki.debian.org/PaulWise
Re: How can I override module name in autopkgtest-pkg-python
I note that my last mail can be confuse The use of debian/tests/pkg-python/import-name is deprecated. But the use of debian/tests/autopkgtest-pkg-python.conf is mentioned on man autodep8. So this can be used. On Wed, Mar 3, 2021 at 7:15 PM Emmanuel Arias wrote: > Hi, > > Maybe this can be useful [0] but that is deprecated. You can create > debian/tests/autopkgtest-pkg-python.conf file and use import_name > variable to change the name. Here an example [1] > > > [0] https://salsa.debian.org/ci-team/autodep8/-/merge_requests/17 > [1] > https://salsa.debian.org/python-team/packages/python-xlib/-/blob/master/debian/tests/autopkgtest-pkg-python.conf > > Cheers, > Emmanuel > > On Wed, Mar 3, 2021 at 5:49 PM Gregor Riepl wrote: > >> > autopkgtest [19:46:36]: test autodep8-python3: set -e ; for py in >> $(py3versions -r 2>/dev/null) ; do cd "$AUTOPKGTEST_TMP" ; echo "Testing >> with $py:" ; $py -c "import cython_blis; print(cython_blis)" ; done >> > autopkgtest [19:46:36]: test autodep8-python3: [--- >> > Testing with python3.9: >> > Traceback (most recent call last): >> > File "", line 1, in >> > ModuleNotFoundError: No module named 'cython_blis' >> > autopkgtest [19:46:37]: test autodep8-python3: ---] >> > >> > >> > The actual module that needs to be importet is just blis. How can >> > I teach autodep8-python3 the correct module name? >> >> Simply write a suitable debian/tests/control file that uses >> >> import blis; print(blis) >> >> instead of >> >> import cython_blis; print(cython_blis) >> >> See here for an example: >> >> https://salsa.debian.org/3dprinting-team/libarcus/-/blob/master/debian/tests/control >> >> Although, it looks like this sort of trivial autopkgtest is now >> considered "superficial" and will no longer reduce the time until a >> package is autopromoted to testing. >> >>
Re: How can I override module name in autopkgtest-pkg-python
Hi, Maybe this can be useful [0] but that is deprecated. You can create debian/tests/autopkgtest-pkg-python.conf file and use import_name variable to change the name. Here an example [1] [0] https://salsa.debian.org/ci-team/autodep8/-/merge_requests/17 [1] https://salsa.debian.org/python-team/packages/python-xlib/-/blob/master/debian/tests/autopkgtest-pkg-python.conf Cheers, Emmanuel On Wed, Mar 3, 2021 at 5:49 PM Gregor Riepl wrote: > > autopkgtest [19:46:36]: test autodep8-python3: set -e ; for py in > $(py3versions -r 2>/dev/null) ; do cd "$AUTOPKGTEST_TMP" ; echo "Testing > with $py:" ; $py -c "import cython_blis; print(cython_blis)" ; done > > autopkgtest [19:46:36]: test autodep8-python3: [--- > > Testing with python3.9: > > Traceback (most recent call last): > > File "", line 1, in > > ModuleNotFoundError: No module named 'cython_blis' > > autopkgtest [19:46:37]: test autodep8-python3: ---] > > > > > > The actual module that needs to be importet is just blis. How can > > I teach autodep8-python3 the correct module name? > > Simply write a suitable debian/tests/control file that uses > > import blis; print(blis) > > instead of > > import cython_blis; print(cython_blis) > > See here for an example: > > https://salsa.debian.org/3dprinting-team/libarcus/-/blob/master/debian/tests/control > > Although, it looks like this sort of trivial autopkgtest is now > considered "superficial" and will no longer reduce the time until a > package is autopromoted to testing. > >
Re: How can I override module name in autopkgtest-pkg-python
> autopkgtest [19:46:36]: test autodep8-python3: set -e ; for py in > $(py3versions -r 2>/dev/null) ; do cd "$AUTOPKGTEST_TMP" ; echo "Testing with > $py:" ; $py -c "import cython_blis; print(cython_blis)" ; done > autopkgtest [19:46:36]: test autodep8-python3: [--- > Testing with python3.9: > Traceback (most recent call last): > File "", line 1, in > ModuleNotFoundError: No module named 'cython_blis' > autopkgtest [19:46:37]: test autodep8-python3: ---] > > > The actual module that needs to be importet is just blis. How can > I teach autodep8-python3 the correct module name? Simply write a suitable debian/tests/control file that uses import blis; print(blis) instead of import cython_blis; print(cython_blis) See here for an example: https://salsa.debian.org/3dprinting-team/libarcus/-/blob/master/debian/tests/control Although, it looks like this sort of trivial autopkgtest is now considered "superficial" and will no longer reduce the time until a package is autopromoted to testing.
Re: Salsa access
On 2021-03-03 07 h 44, Stephan Lachnit wrote: > Dear team members, > > boolean.py is a python package that just landed in Unstable. > I would like to transfer the repo from my namespace to the team namespace, > since the team is also named as maintainer. > > Can someone give me maintainer access so I can move it? Hi! If you intend to maintain the package in the Team, you need to follow this procedure: https://salsa.debian.org/python-team/tools/python-modules/-/blob/master/policy.rst#joining-the-team Cheers, -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Louis-Philippe Véronneau ⢿⡄⠘⠷⠚⠋ po...@debian.org / veronneau.org ⠈⠳⣄ OpenPGP_signature Description: OpenPGP digital signature
joining the team
Hello Pythonistas, I would like to join the Python team. I help maintaining some Golang packages and would like to help maintaining Python packages as well since Python is my primary language of daily use. I have read the policy and I agree. My salsa login is dundee. I would be glad for some tips for first work. Thanks Daniel OpenPGP_0xEF0BA1C4F3990103.asc Description: application/pgp-keys OpenPGP_signature Description: OpenPGP digital signature
How can I override module name in autopkgtest-pkg-python
Hi, I worked on the package python-cython-blis[1] (there is no specific reason to have it in Debian Science scope - I just found an existing repository there and continued with this). The package works nicely - but the autopkgtest (in Salsa CI[2] does not): autopkgtest [19:46:36]: test autodep8-python3: set -e ; for py in $(py3versions -r 2>/dev/null) ; do cd "$AUTOPKGTEST_TMP" ; echo "Testing with $py:" ; $py -c "import cython_blis; print(cython_blis)" ; done autopkgtest [19:46:36]: test autodep8-python3: [--- Testing with python3.9: Traceback (most recent call last): File "", line 1, in ModuleNotFoundError: No module named 'cython_blis' autopkgtest [19:46:37]: test autodep8-python3: ---] The actual module that needs to be importet is just blis. How can I teach autodep8-python3 the correct module name? Kind regards Andreas. [1] https://salsa.debian.org/science-team/python-cython-blis [2] https://salsa.debian.org/science-team/python-cython-blis/-/jobs/1483087 -- http://fam-tille.de
Re: Need a Python 3.8 virtual environment
On Wed, Mar 3, 2021 at 8:56 AM Steven Robbins wrote: > > Hi, > > I'm trying to use a (non-Debian) python system built on python 3.8. Debian's > default is currently 3.9 so I am advised to use a virtual environment. Being > a newbie, I searched around and found a writeup covering several different > virtualization tools [1]. Note I am using Debian 'sid'. > > I can use the tool "virtualenv" to create a virtual environment for default > python: > > steve@riemann:/tmp$ virtualenv blah > created virtual environment CPython3.9.1.final.0-64 in 77ms > creator CPython3Posix(dest=/tmp/blah, clear=False, no_vcs_ignore=False, > global=False) > seeder FromAppData(download=False, pip=bundle, setuptools=bundle, > wheel=bundle, via=copy, app_data_dir=/home/steve/.local/share/virtualenv) > added seed packages: pip==20.1.1, pkg_resources==0.0.0, > setuptools==44.0.0, wheel==0.34.2 > activators > BashActivator,CShellActivator,FishActivator,PowerShellActivator,PythonActivator,XonshActivator > > > But not for python 3.8: > > steve@riemann:/tmp$ virtualenv -p python3.8 blah38 > RuntimeError: failed to find interpreter for Builtin discover of > python_spec='python3.8' > > > I have installed literally all the Debian python packages whose name contains > 'python3.8'. A very short list: > > ii libpython3.8:amd643.8.7-1 > amd64Shared Python runtime library (version 3.8) > ii libpython3.8-dev:amd643.8.7-1 > amd64Header files and a static library for Python (v3.8) > ii libpython3.8-minimal:amd643.8.7-1 > amd64Minimal subset of the Python language (version 3.8) > ii libpython3.8-stdlib:amd64 3.8.7-1 > amd64Interactive high-level object-oriented language (standard > library, version 3.8) > ii python3.8 3.8.7-1 > amd64Interactive high-level object-oriented language (version 3.8) > ii python3.8-dev 3.8.7-1 > amd64Header files and a static library for Python (v3.8) > ii python3.8-minimal > > > > I have also tried the module 'venv': > > steve@riemann:/tmp$ python3.8 -m venv v38 > The virtual environment was not created successfully because ensurepip is not > available. On Debian/Ubuntu systems, you need to install the python3-venv > package using the following command. > > apt-get install python3-venv > > You may need to use sudo with that command. After installing the python3-venv > package, recreate your virtual environment. > > Failing command: ['/tmp/v38/bin/python3.8', '-Im', 'ensurepip', '--upgrade', > '--default-pip'] > > steve@riemann:/tmp$ python3.8 -m venv blah38 > The virtual environment was not created successfully because ensurepip is not > available. On Debian/Ubuntu systems, you need to install the python3-venv > package using the following command. > > apt-get install python3-venv > > You may need to use sudo with that command. After installing the python3-venv > package, recreate your virtual environment. > > Failing command: ['/tmp/blah38/bin/python3.8', '-Im', 'ensurepip', '-- > upgrade', '--default-pip'] > > > Note that I do have 'python3-venv' installed, but it is the 3.9 version: > ii python3-venv 3.9.1-1 > amd64pyvenv-3 binary for python3 (default python3 version) > > > Is there something I've missed? > > Thank you, > -Steve > > [1] > https://linuxconfig.org/how-to-set-up-a-python-virtual-environment-on-debian-10-buster try using pyenv https://mentors.debian.net/package/pyenv/
Re: Need a Python 3.8 virtual environment
On 3/3/21 6:56 PM, Andrey Rahmatullin wrote: > On Wed, Mar 03, 2021 at 05:39:04PM +, Stefano Rivera wrote: >> You need python3.8-venv. > Which doesn't exist, at least in the current repos. you rebuild it from python3-stdlib-extensions. but yes, the binaries don't exist in the archive.
Re: Need a Python 3.8 virtual environment
On Wed, Mar 03, 2021 at 05:39:04PM +, Stefano Rivera wrote: > You need python3.8-venv. Which doesn't exist, at least in the current repos. -- WBR, wRAR signature.asc Description: PGP signature
Re: Need a Python 3.8 virtual environment
Hi Steven (2021.03.03_03:17:36_+) > steve@riemann:/tmp$ python3.8 -m venv blah38 > The virtual environment was not created successfully because ensurepip is not > available. On Debian/Ubuntu systems, you need to install the python3-venv > package using the following command. > > apt-get install python3-venv > > You may need to use sudo with that command. After installing the python3-venv > package, recreate your virtual environment. > > Failing command: ['/tmp/blah38/bin/python3.8', '-Im', 'ensurepip', '-- > upgrade', '--default-pip'] > > > Note that I do have 'python3-venv' installed, but it is the 3.9 version: > ii python3-venv 3.9.1-1 > > amd64pyvenv-3 binary for python3 (default python3 version) > > > Is there something I've missed? You need python3.8-venv. But even then you may run into a missing/incompatible distutils (#979819): https://bugs.debian.org/979819 You can see if you have, by running the failing ensurepip command by hand. Hopefully we'll make that situation better soon... BTW: There's a deadsnakes-like archive for Debian: https://people.debian.org/~paravoid/python-all/ SR -- Stefano Rivera http://tumbleweed.org.za/ +1 415 683 3272
Re: Need a Python 3.8 virtual environment
On 2021-03-03 10:45:46 + (+), Julien Palard wrote: [...] > I'm using a bash function [1] to easily recompile needed Pythons (I test > some projects with Python 3.5 to 3.9), but it's not that hard without my > bash function: [...] This is pretty much identical to how I tackle it too, though I build from tags checked out of the cpython Git repository. If you're looking for prebuilt debs, I know some folks use this, from what I understand the packages should be compatible with reasonably contemporary Debian releases: https://launchpad.net/~deadsnakes/+archive/ubuntu/ppa -- Jeremy Stanley signature.asc Description: PGP signature
Re: Need a Python 3.8 virtual environment
On Wed, Mar 03, 2021 at 08:32:01AM -0500, Yaroslav Halchenko wrote: > > I'm trying to use a (non-Debian) python system built on python 3.8. > > Debian's > > default is currently 3.9 so I am advised to use a virtual environment. > > Being > > a newbie, I searched around and found a writeup covering several different > > virtualization tools [1]. Note I am using Debian 'sid'. > > I know that it is not a "proper" Debian answer Sure, the only proper Debian answer would be "actually you don't need this version". -- WBR, wRAR signature.asc Description: PGP signature
Re: Need a Python 3.8 virtual environment
On Tue, 02 Mar 2021, Steven Robbins wrote: > Hi, > I'm trying to use a (non-Debian) python system built on python 3.8. Debian's > default is currently 3.9 so I am advised to use a virtual environment. > Being > a newbie, I searched around and found a writeup covering several different > virtualization tools [1]. Note I am using Debian 'sid'. I know that it is not a "proper" Debian answer, but in such cases I just quickly install miniconda with a needed python version. I keep a miniconda installation with conda environments for different Pythons for such cases. -- Yaroslav O. Halchenko Center for Open Neuroscience http://centerforopenneuroscience.org Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755 WWW: http://www.linkedin.com/in/yarik
Salsa access
Dear team members, boolean.py is a python package that just landed in Unstable. I would like to transfer the repo from my namespace to the team namespace, since the team is also named as maintainer. Can someone give me maintainer access so I can move it? Regards, Stephan
Re: Need a Python 3.8 virtual environment
Le 2021-03-03 à 04:17, Steven Robbins a écrit : > I'm trying to use a (non-Debian) python system built on python 3.8. Debian's > default is currently 3.9 so I am advised to use a virtual environment. As other told, the right way is probably to compile it yourself (or use pyenv, but I don't like pyenv "shims", I prefer to keep it simple). I'm using a bash function [1] to easily recompile needed Pythons (I test some projects with Python 3.5 to 3.9), but it's not that hard without my bash function: apt install make build-essential libbz2-dev liblzma-dev libssl-dev llvm libreadline-dev libncurses5-dev libffi-dev zlib1g-dev tk-dev libsqlite3-dev xz-utils wget the version you want from https://www.python.org/ftp/python tar -xzf it ./configure --prefix=$HOME/.local/ make -j $(nproc) make altinstall You'll get a `python3.8` binary in ~/.local/bin, you can create venvs with it as: python3.8 -m venv the_venv_path [1]: https://github.com/JulienPalard/dotfiles/blob/0b5feb79b1ba648b7212162b68da5a182e0341c1/.bashrc#L196 -- [Julien Palard](https://mdk.fr)
Re: Need a Python 3.8 virtual environment
Hi Steven, On Tue, Mar 02, 2021 at 09:17:36PM -0600, Steven Robbins wrote: > I'm trying to use a (non-Debian) python system built on python 3.8. Debian's > ... > Is there something I've missed? Do you know https://github.com/saghul/pythonz ? I do not use it myself, but a colleague told me he uses that when he needs to test something with every python version available. Hope this helps. -- Nicolas Chauvat logilab.fr - services en informatique scientifique et gestion de connaissances
