[prev in list] [next in list] [prev in thread] [next in thread]
List: fedora-devel-list
Subject: Re: Heads Up: python2 is marked as deprecated
From: Tomasz_Kłoczko <kloczko.tomasz () gmail ! com>
Date: 2018-09-11 18:52:31
Message-ID: CABB28Cwi=wJXDLzzeqf0eE=LPZmNZ4B90_sz7p=9EkufAzLLDQ () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
On Tue, 11 Sep 2018 at 16:48, Petr Viktorin <pviktori@redhat.com> wrote:
[..]
> These numbers hide an important fact: many things currently come with
> RPMs for both python2 and python3.
>
> More detailed statistics (based on SRPMs, not binary RPMs):
> http://fedora.portingdb.xyz/
> Graph with historical data: http://fedora.portingdb.xyz/history/
>
> > In other words trying currently announcing python2 as depricated is at
> > least a bit .. odd.
>
> Do you know a better way to make the python2 numbers go down?
>
> Would *you* be interested in maintaining python2 past 2020, with no
> upstream support and 3415 dependent packages?
>
No and no .. of course :)
I've been only trying to say that with current numbers about balance
between python 2 and 3 packages are making announcement about deprecation a
bit to early. Only this and nothing more :P
I fully understand effort to migrate ASAP to python 3.
IMO it should be announced only kind of call to migrate as much as possible
with completing set of advises abut typical porting issues.
Forming ad hoc team people which could help porting code to python 3 may
IMO be useful.
I have in my set of packages one of those which will require migration to
python 3 as well.
It is mc package which has amazon s3 vfs backend as and
I'm thinking about create mc-s3 (or mc-vfs-s3) subpackage to separate
python2 dependent parts.
Theoretically as now aws-cli AFAIK is already ported to python 3 it should
be easy however I haven't now access to AWS systems to test s3 bucket
access over mc.
Other possible option may be rewrite s3 vfs backent to use some other (non
python based script .. and backend tool).
kloczek
--
Tomasz Kłoczko | LinkedIn: http://lnkd.in/FXPWxH
[Attachment #5 (text/html)]
<div dir="ltr"><div class="gmail_default" \
style="font-family:monospace,monospace"><span \
style="font-family:Arial,Helvetica,sans-serif">On Tue, 11 Sep 2018 at 16:48, Petr \
Viktorin <<a href="mailto:pviktori@redhat.com">pviktori@redhat.com</a>> \
wrote:</span></div><div class="gmail_default" \
style="font-family:monospace,monospace"><span \
style="font-family:Arial,Helvetica,sans-serif">[..]</span></div><div \
class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 \
.8ex;border-left:1px #ccc solid;padding-left:1ex"> These numbers hide an important \
fact: many things currently come with <br> RPMs for both python2 and python3.<br>
<br>
More detailed statistics (based on SRPMs, not binary RPMs): <br>
<a href="http://fedora.portingdb.xyz/" rel="noreferrer" \
target="_blank">http://fedora.portingdb.xyz/</a><br> Graph with historical data: <a \
href="http://fedora.portingdb.xyz/history/" rel="noreferrer" \
target="_blank">http://fedora.portingdb.xyz/history/</a><br> <br>
> In other words trying currently announcing python2 as depricated is at <br>
> least a bit .. odd.<br>
<br>
Do you know a better way to make the python2 numbers go down?<br>
<br>
Would *you* be interested in maintaining python2 past 2020, with no <br>
upstream support and 3415 dependent packages?<br></blockquote><div><br></div><div \
class="gmail_default" style="font-family:monospace,monospace">No and no .. of course \
:)</div><div class="gmail_default" style="font-family:monospace,monospace">I've \
been only trying to say that with current numbers about balance between python 2 and \
3 packages are making announcement about deprecation a bit to early. Only this and \
nothing more :P</div><div class="gmail_default" \
style="font-family:monospace,monospace">I fully understand effort to migrate ASAP to \
python 3.</div><div class="gmail_default" style="font-family:monospace,monospace">IMO \
it should be announced only kind of call to migrate as much as possible with \
completing set of advises abut typical porting issues.</div><div \
class="gmail_default" style="font-family:monospace,monospace">Forming ad hoc team \
people which could help porting code to python 3 may IMO be useful.</div><div \
class="gmail_default" style="font-family:monospace,monospace"><br></div><div \
class="gmail_default" style="font-family:monospace,monospace">I have in my set of \
packages one of those which will require migration to python 3 as well.</div><div \
class="gmail_default" style="font-family:monospace,monospace">It is mc package which \
has amazon s3 vfs backend as and </div><div class="gmail_default" \
style="font-family:monospace,monospace">I'm thinking about create mc-s3 (or \
mc-vfs-s3) subpackage to separate python2 dependent parts.</div><div \
class="gmail_default" style="font-family:monospace,monospace">Theoretically as now \
aws-cli AFAIK is already ported to python 3 it should be easy however I haven't \
now access to AWS systems to test s3 bucket access over mc.</div><div \
class="gmail_default" style="font-family:monospace,monospace"></div><div \
class="gmail_default" style="font-family:monospace,monospace">Other possible option \
may be rewrite s3 vfs backent to use some other (non python based script .. and \
backend tool).</div><div class="gmail_default" \
style="font-family:monospace,monospace"><br></div><div><font face="monospace, \
monospace"><span class="gmail_default" \
style="font-family:monospace,monospace">kloczek</span><br \
class="gmail-Apple-interchange-newline">-- </font></div><div dir="ltr"><font \
face="monospace, monospace">Tomasz Kłoczko | LinkedIn: <span \
style="text-decoration-line:underline;font-size:13px;background-color:transparent;vertical-align:baseline;white-space:pre-wrap"><a \
href="http://lnkd.in/FXPWxH" target="_blank" \
style="text-decoration-line:none">http://lnkd.in/FXPWxH</a></span></font></div></div></div>
[Attachment #6 (text/plain)]
_______________________________________________
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-leave@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic