Re: Joining the team! Again with policy acceptance.
On Sunday, March 5, 2023 12:51:59 PM EST Scarlett Moore wrote: > Hi! > My name is Scarlett Moore, I have been working on https://salsa.debian.org/ > mycroftai-team which consists of many python packages relating to voice AI. > Mycroft is no more, but forked. I would like to move these packages to the > python umbrella so as to be useful everywhere and of course consistency, > team maintained. I will of course continue maintaining and not dump them > here, I will also help elsewhere as needed. > I have read and accept > https://salsa.debian.org/python-team/tools/python-modules/blob/master/polic > y.rst My salsa ID is @sgmoore. > Thank you for your consideration, > Scarlett Welcome to the team. Scott K signature.asc Description: This is a digitally signed message part.
Joining the team! Again with policy acceptance.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hi! My name is Scarlett Moore, I have been working on https://salsa.debian.org/ mycroftai-team which consists of many python packages relating to voice AI. Mycroft is no more, but forked. I would like to move these packages to the python umbrella so as to be useful everywhere and of course consistency, team maintained. I will of course continue maintaining and not dump them here, I will also help elsewhere as needed. I have read and accept https://salsa.debian.org/python-team/tools/python-modules/blob/master/policy.rst My salsa ID is @sgmoore. Thank you for your consideration, Scarlett -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEfDWSDxziiZ6OqarQLnwDZ7m/oIkFAmQE1r8ACgkQLnwDZ7m/ oImjUA//eYZKmfYJCl2v0S0++q7ju5Efjw7hrSUn554AIggB6jZQQE67frXsUaXx Tqkyr6Xb1UqQqUi9SEkzTi0TdmxKvSUdN+YE56h6rT00w208Hr2nrp9GAqEYsrfS WbZfGukjstAoNRgEphOzAYUhcr+/xeswzeRln3C1bWeC1OFPKJ+ghXGEcOfaUGKN OT5RligVKN3qrm/oAw0S9V4vGq2p7LaEG+NBDvkYEwuJBdWL3uzxa6O3DYMUF1jU bhoWYEqUcw1kSkcDt/LR4P3rn0QJ3A7Sa7r3uRQXXkiItQRcB6q7s/nu6LszIICL gLPjrFJx3cuctB6sbb+4ykRlaw8zGs2nc0zkNb7QG7LF6b8bOYqhtzuHSrbso1Jd jO5tkB0jD/V9NVA3ZUxpOrH/0XFD0wPbUldgk+mbuZAoOVW2o8Yfr2fvsblADNvw txbjUkbH1GZesYsgCSCp67cOeDVRABbI9GkzIcP16qtS5a63ZYO/eVx5uZe/mtSd XkN5qGO85Hw0r14/+tKyFJklZ+lYaAN9uTIBYmNlbk2v8yz4wpbFsZjA7FN0Dmyv DJ/xi/eqXkq0LogOIhW+6amA2ETd4h5RgFZkJ/IGep2bsHQ33COmtK+QTF1cIQfV vpqoxmMIoCgSCufa3tiqYJw83rbfuglEf9iO6UedbPRf1c4sTF4= =DFnJ -END PGP SIGNATURE-
Joining the team! Please
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hi! My name is Scarlett Moore, I have been working on https://salsa.debian.org/ mycroftai-team which consists of many python packages relating to voice AI. Mycroft is no more, but forked. I would like to move these packages to the python umbrella so as to be useful everywhere and of course consistency, team maintained. I will of course continue maintaining and not dump them here, I will also help elsewhere as needed. My salsa ID is @sgmoore. Thank you for your consideration, Scarlett -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEfDWSDxziiZ6OqarQLnwDZ7m/oIkFAmQE1GcACgkQLnwDZ7m/ oImRUxAAsElJoZP6i0A0KDIvSrgKbqMIh3m2+Oi0TFp5OKLeA5hK2lRYkrJJF735 b9Fr3lp5ppHT6xEIrYOqIzp48Fm6FuJxq5p/hawSywdIYxLrG3SE/W9D1ot6PeoH ZurbkYBpXIP8hiGEEIFfVbJN+rEcmOJNkjnsVEnSJuMzwySFVfF1g5MNIrb/9J0c dMk9oHPNvyJCbEavCxLPAGCoIdoMWYHOFdU0XyOnHrTH4YbeBrmY6ZjZRPnRE/8q /jkePjx2kAOiN/yjSityjgTIrz/hDLHrFM08ZD+B6p/IKK62b40+HnbZxfOEyuBA Mpl0r1hja6QJaWJjnm6gVj4pP+GfuLFFhmLHESn+nnK8DrX8BPJbtyTN5Awk4Jzm +No42B/wNCbdY1a0enn3HZg84V6+VVDA2v3Qf2IsveiARyZ2fjyQRYsWOt4Tt5/I yvqvVPZoGEg8Yv7RbledZlUI71W9Xizg6IdRBEt9rgc0AY27YfcwYy13WgM0FGJT MpViklpuplD86bUFjXwiA2va6uyGRobgscyyFhFEZavDjk9vVqyx6Vc8zeAQtOyV vrmqjn1A/Jx1Bky3e7pGA2JQ3PoadHq683R5x+ss3XwNTK3MEYe/54G5yhYPdQNO nvq/Kn2N4qoZrV2VlA+XuHBKbPdMrVebVSy8IAi5ddFo5u/jXg0= =thmq -END PGP SIGNATURE-
Re: #!/usr/bin/python3 vs virtualenv
(sorry for replying to a random message, I am not subscribed to the list) I don't use `sudo pip`, too risky. I used to use pip to install packages with the implicit --user option (for things not available via apt). And I am aware of --break-system-packages, I used it the first time pip complained about an externally managed environment so I could keep working as before. I decided to follow the recommandations and use a virtual environment. And, in order to benefit from the packaging done in Debian, I thought I could use --system-site-packages and restrict pip to a few things that Debian does not provide. I now see that this was too optimistic. For now I'll use `python -m sphinx.cmd.build` as a workaround, but the next time I hit some issue I'll probably end up using conda, like everyone else. It just feels sad to see all the effort done in packaging Python things in Debian end with the recommendation not to use them :-( Thank you all for the advice, -- Marc Glisse
Re: #!/usr/bin/python3 vs virtualenv
FWIW, I am one of those power users that develop python applications and prefer the simplicity of a single environment. In my personal experience, installing using `sudo pip` (or user pip, which I don't do at all) is not a frequent operation for users that choose to manage a single environment. Personally, I use it only after searching in apt and confirming the package is not there. Having to type --break-system-packages every time when I have to do it is a good solution for me that I find completely reasonable. Thank you! On Sun, Mar 5, 2023 at 5:47 AM Julian Gilbey wrote: > On Fri, Mar 03, 2023 at 04:22:11PM -0500, Jorge Moraleda wrote: > > Jeremy, Thank you for your quick reply! > > > > I did not know about `sudo pip install --break-system-packages foo` or > `sudo rm > > /usr/lib/python3.11/EXTERNALLY-MANAGED` (Frankly I only knew about this > issue > > what I have read on this discussion). This is very helpful and it really > changes > > my outlook on this topic. > > The --break-system-packages option is noted in > /usr/share/doc/python3.11/README.venv, and this file is mentioned in > the NEWS file for python3.11. The > /usr/lib/python3.11/EXTERNALLY-MANAGED file is not mentioned there; I > personally think that having to type --break-system-packages every > time one installs a package via pip globally or on a per-user basis is > safer, as it reminds you that you run risks doing so. > > Best wishes, > >Julian >
Re: #!/usr/bin/python3 vs virtualenv
On Fri, Mar 03, 2023 at 04:22:11PM -0500, Jorge Moraleda wrote: > Jeremy, Thank you for your quick reply! > > I did not know about `sudo pip install --break-system-packages foo` or `sudo > rm > /usr/lib/python3.11/EXTERNALLY-MANAGED` (Frankly I only knew about this issue > what I have read on this discussion). This is very helpful and it really > changes > my outlook on this topic. The --break-system-packages option is noted in /usr/share/doc/python3.11/README.venv, and this file is mentioned in the NEWS file for python3.11. The /usr/lib/python3.11/EXTERNALLY-MANAGED file is not mentioned there; I personally think that having to type --break-system-packages every time one installs a package via pip globally or on a per-user basis is safer, as it reminds you that you run risks doing so. Best wishes, Julian
