Marco Minutoli wrote:
> Hello,
>
> I have experienced difficulties in upgrading my system as a
> consequence of the python 3.12 update. I am aware that there is a
> "fervent" discussion on the topic [1], but I decided to keep my
> distance from those spicy tones and I hope for a more polite
> conversation here.
>
> Let me premise, that I don't want to question the decision of
> switching the default. I am sure that the people who took that
> decision did it for some good reason. However, allow me to make the
> point that the user experience in this upgrade was unnecessarily painful.
>
> In fact if you read through the colorful conversation on the gentoo
> forum, you'll notice that some well-known (or important to some)
> packages are not ready/compatible with python 3.12 on gentoo stable.
> FreeCAD and KiCAD are those important to me as I use them for my
> hobbies. Clearly I have really low stakes. Nevertheless, we can agree
> that there might be people using Gentoo that want to produce income
> with their systems. Therefore, breaking anything marked as "stable"
> with a version upgrade seems unnecessary on the user side.
>
> I decided to fix my system by sticking to python 3.11 and, as a user,
> I would greatly appreciate news alerting us when the whole stable tree
> becomes compatible with python 3.12. However, I am wondering if
> staying with python 3.11 implies that I won't be able to use the
> binary packages depending on python.
>
> In my attempt to fix my own system I tried to follow the road of
> having both python 3.11 and 3.12 and that resulted in an extremely
> long list of packages for which binaries were not available. As of
> today, binaries with support for python 3.11 are available. How long
> will that support last?
>
> Am I better off unmerging FreeCAD and KiCAD, using AppImages, and
> upgrading my system to python 3.12? As a user, this would feel really
> wrong.
>
> Best regards,
> Marco.
>
> [1] 
> https://forums.gentoo.org/viewtopic-p-8828818.html?sid=d9a82c4e691be29249059bcb9d86a8e1


I was caught up in the upgrade problem too.  Each time I would run
emerge, I would get more packages that can't use 3.12 yet.  This is the
list if packages I had to add to package.use.


######################################################
# Try to remove soon.  Also sci-electronics/kicad further down.
app-admin/checkrestart python_single_target_python3_11
app-portage/elogviewer python_single_target_python3_11
dev-python/platformdirs python_targets_python3_11
dev-python/setuptools-scm python_targets_python3_11
net-libs/gupnp python_single_target_python3_11
dev-python/packaging python_targets_python3_11
dev-python/setuptools python_targets_python3_11
dev-python/gpep517 python_targets_python3_11
dev-python/flit-core python_targets_python3_11
dev-python/installer python_targets_python3_11
dev-python/jaraco-text python_targets_python3_11
dev-python/more-itertools python_targets_python3_11
dev-python/ordered-set python_targets_python3_11
dev-python/wheel python_targets_python3_11
dev-python/jaraco-context python_targets_python3_11
dev-python/jaraco-functools python_targets_python3_11
media-libs/avidemux-plugins python_single_target_python3_11
sys-apps/portage python_targets_python3_11
app-portage/gemato python_targets_python3_11
dev-python/requests python_targets_python3_11
dev-python/certifi python_targets_python3_11
dev-python/charset-normalizer python_targets_python3_11
dev-python/idna python_targets_python3_11
dev-python/urllib3 python_targets_python3_11
dev-python/PySocks python_targets_python3_11
dev-python/hatchling python_targets_python3_11
dev-libs/boost python_targets_python3_11
dev-python/editables python_targets_python3_11
dev-python/pathspec python_targets_python3_11
dev-python/pluggy python_targets_python3_11
dev-python/trove-classifiers python_targets_python3_11
dev-python/sip python_targets_python3_11
dev-python/dbus-python python_targets_python3_11
######################################################

I have other USE flags for Kicad so it is further down.  Anyway, there
is a lot of packages that are not ready for 3.12 yet.  Thing is, at some
point, they have to switch even if some are not ready.  There is always
some packages that are slow to update.  Lack of maintainer, very
difficult to build and lots of time to test etc etc.  There is sometimes
a good reason some packages drag behind a bit. 

I also agree that it would be nice if they would do a news item or
something to let us know when 3.12 is ready for virtually all packages. 
As you can see from my list above, I included a statement to remove
later and see if it works. 

The one thing I wish emerge would do in cases like this, spit out all
packages at once that need changes.  A lot of those were done one or
maybe two packages at a time.  My CPU had to be bored to tears running
emerge that many times.  ROFL 

I hope that list above helps someone.  Maybe copy and paste it. 

Dale

:-)  :-) 

Reply via email to