1:29 a.m.
Hi folks,
During the discussion of the os.urandom() change in Python 3.6 (the
successor to the accidental change in Python 3.5 that is the subject
of Tomas's emailing about rebasing to 3.5.2 in F24), we came to the
conclusion it would be good to get 3.6 into Rawhide early enough to
impact the upstream beta cycle:
https://lists.fedorahosted.org/archives/list/python-devel@lists.fedorapro...
However, there's no reference to that discussion in
https://fedoraproject.org/wiki/Changes/Python3.6 - it only refers to
incorporating a release candidate or the actual release, which will be
too late for us to request changes to the upstream default
os.urandom() behaviour if we find unexpected problems with it.
With Python 3.6b2 recently pushed out the door, there's about two
months (including two more beta releases) until the first release
candidate in early December.
Regards,
Nick.
--
Nick Coghlan | ncoghlan(a)gmail.com | Brisbane, Australia
6:15 a.m.
Hello Nick,
Please feel free to edit the change proposal. I also fully agree to the proposal you made
at the link you provided. Currently I have in copr the first beta, and also I can build
the second beta as well if I exclude the ensurepip test.
I was actually thinking of adding python 3.6 in rawhide when rc1 was released, but if that
is too late, which pre-release would be ideal to be built in rawhide?
Regards,
Charalampos Stratakis
Associate Software Engineer
Python Maintenance Team, Red Hat
----- Original Message -----
From: "Nick Coghlan" <ncoghlan(a)gmail.com>
To: "Fedora Python SIG" <python-devel(a)lists.fedoraproject.org>
Sent: Wednesday, October 12, 2016 8:29:04 AM
Subject: Python 3.6 beta release in F26 Rawhide?
Hi folks,
During the discussion of the os.urandom() change in Python 3.6 (the
successor to the accidental change in Python 3.5 that is the subject
of Tomas's emailing about rebasing to 3.5.2 in F24), we came to the
conclusion it would be good to get 3.6 into Rawhide early enough to
impact the upstream beta cycle:
https://lists.fedorahosted.org/archives/list/python-devel@lists.fedorapro...
However, there's no reference to that discussion in
https://fedoraproject.org/wiki/Changes/Python3.6 - it only refers to
incorporating a release candidate or the actual release, which will be
too late for us to request changes to the upstream default
os.urandom() behaviour if we find unexpected problems with it.
With Python 3.6b2 recently pushed out the door, there's about two
months (including two more beta releases) until the first release
candidate in early December.
Regards,
Nick.
--
Nick Coghlan | ncoghlan(a)gmail.com | Brisbane, Australia
_______________________________________________
python-devel mailing list -- python-devel(a)lists.fedoraproject.org
To unsubscribe send an email to python-devel-leave(a)lists.fedoraproject.org
1:19 a.m.
On 12 October 2016 at 21:15, Charalampos Stratakis <cstratak(a)redhat.com> wrote:
Hello Nick,
Please feel free to edit the change proposal. I also fully agree to the proposal you made
at the link you provided. Currently I have in copr the first beta, and also I can build
the second beta as well if I exclude the ensurepip test.
I was actually thinking of adding python 3.6 in rawhide when rc1 was released, but if
that is too late, which pre-release would be ideal to be built in rawhide?
The earliest one we can get FESCo to approve as a system-wide change
for Fedora 26 :)
That probably means beta 3 at this point - that's due out in two weeks
time (October 31), so we'd be seeking FESCo approval for the change
and pre-release Rawhide testing plan either this Friday or next
Friday.
If we decide that timeline is too ambitious (accounting for the fact
I'm on vacation next week), then we'd target beta 4 on November 21st,
allowing:
- COPR-based testing of b2 and b3 to minimise stability impact to F26 Rawhide
- incorporation of F26 Rawhide feedback into the upstream 3.6.0rc1
FESCo may come back and say "No, stick with the original rc1 plan", in
which case the approach would change to assume we'll carry a patch for
the os.urandom warning until at least 3.6.1, but hopefully we can make
the case that b4 will be stable *enough*, and that if there are
unexpectedly compatibility bugs, we're much better off finding them
while there's time to submit fixes for them back upstream.
Cheers,
Nick.
--
Nick Coghlan | ncoghlan(a)gmail.com | Brisbane, Australia
4:26 a.m.
Hi,
The change is already approved by FESCo [0] although as mentioned at the change page, it
is accepted for release candidate, so I guess I should open another ticket for FESCo if
they agree for a beta version to be built in rawhide.
Copr builds are here [1] as well (although not announced in any mailing list yet).
[0] https://fedoraproject.org/wiki/Releases/26/ChangeSet?rd=Releases/26
[1] https://copr.fedorainfracloud.org/coprs/cstratak/python-3.6/build/464733/
Regards,
Charalampos Stratakis
Associate Software Engineer
Python Maintenance Team, Red Hat
----- Original Message -----
From: "Nick Coghlan" <ncoghlan(a)gmail.com>
To: "Fedora Python SIG" <python-devel(a)lists.fedoraproject.org>
Sent: Monday, October 17, 2016 8:19:28 AM
Subject: Re: Python 3.6 beta release in F26 Rawhide?
On 12 October 2016 at 21:15, Charalampos Stratakis <cstratak(a)redhat.com> wrote:
Hello Nick,
Please feel free to edit the change proposal. I also fully agree to the proposal you made
at the link you provided. Currently I have in copr the first beta, and also I can build
the second beta as well if I exclude the ensurepip test.
I was actually thinking of adding python 3.6 in rawhide when rc1 was released, but if
that is too late, which pre-release would be ideal to be built in rawhide?
The earliest one we can get FESCo to approve as a system-wide change
for Fedora 26 :)
That probably means beta 3 at this point - that's due out in two weeks
time (October 31), so we'd be seeking FESCo approval for the change
and pre-release Rawhide testing plan either this Friday or next
Friday.
If we decide that timeline is too ambitious (accounting for the fact
I'm on vacation next week), then we'd target beta 4 on November 21st,
allowing:
- COPR-based testing of b2 and b3 to minimise stability impact to F26 Rawhide
- incorporation of F26 Rawhide feedback into the upstream 3.6.0rc1
FESCo may come back and say "No, stick with the original rc1 plan", in
which case the approach would change to assume we'll carry a patch for
the os.urandom warning until at least 3.6.1, but hopefully we can make
the case that b4 will be stable *enough*, and that if there are
unexpectedly compatibility bugs, we're much better off finding them
while there's time to submit fixes for them back upstream.
Cheers,
Nick.
--
Nick Coghlan | ncoghlan(a)gmail.com | Brisbane, Australia
_______________________________________________
python-devel mailing list -- python-devel(a)lists.fedoraproject.org
To unsubscribe send an email to python-devel-leave(a)lists.fedoraproject.org
9:22 a.m.
On 17 October 2016 at 19:26, Charalampos Stratakis <cstratak(a)redhat.com> wrote:
Hi,
The change is already approved by FESCo [0] although as mentioned at the change page,
Aye, I'd missed that initially, and then saw the ChangeAccepted note on the BZ.
it is accepted for release candidate, so I guess I should open
another ticket for FESCo if they agree for a beta version to be built in rawhide.
Let's see how far we can get with COPR builds before going back to
FESCo - we should at least run
https://beaker-project.org/docs/user-guide/beaker-provided-tasks.html#dis...
against the COPR Python and the Fedora packages that depend on Python
before proposing early adoption of the betas.
(Although I'll have to ask what's become of beaker.fedoraproject.org
before doing that - if it's not going to be back any time soon, then I
may need to run that on the Red Hat internal instance instead)
Cheers,
Nick.
--
Nick Coghlan | ncoghlan(a)gmail.com | Brisbane, Australia
9:49 a.m.
The current URL should be https://beaker.qa.fedoraproject.org/ if that is the one you have
in mind.
Regards,
Charalampos Stratakis
Associate Software Engineer
Python Maintenance Team, Red Hat
----- Original Message -----
From: "Nick Coghlan" <ncoghlan(a)gmail.com>
To: "Fedora Python SIG" <python-devel(a)lists.fedoraproject.org>
Sent: Monday, October 17, 2016 4:22:20 PM
Subject: Re: Python 3.6 beta release in F26 Rawhide?
On 17 October 2016 at 19:26, Charalampos Stratakis <cstratak(a)redhat.com> wrote:
Hi,
The change is already approved by FESCo [0] although as mentioned at the change page,
Aye, I'd missed that initially, and then saw the ChangeAccepted note on the BZ.
it is accepted for release candidate, so I guess I should open
another ticket for FESCo if they agree for a beta version to be built in rawhide.
Let's see how far we can get with COPR builds before going back to
FESCo - we should at least run
https://beaker-project.org/docs/user-guide/beaker-provided-tasks.html#dis...
against the COPR Python and the Fedora packages that depend on Python
before proposing early adoption of the betas.
(Although I'll have to ask what's become of beaker.fedoraproject.org
before doing that - if it's not going to be back any time soon, then I
may need to run that on the Red Hat internal instance instead)
Cheers,
Nick.
--
Nick Coghlan | ncoghlan(a)gmail.com | Brisbane, Australia
_______________________________________________
python-devel mailing list -- python-devel(a)lists.fedoraproject.org
To unsubscribe send an email to python-devel-leave(a)lists.fedoraproject.org
9:57 a.m.
On 18 October 2016 at 00:49, Charalampos Stratakis <cstratak(a)redhat.com> wrote:
The current URL should be https://beaker.qa.fedoraproject.org/ if
that is the one you have in mind.
Indeed it is, thank you!
Cheers,
Nick.
--
Nick Coghlan | ncoghlan(a)gmail.com | Brisbane, Australia
5:53 p.m.
On 10/17/2016 10:57 AM, Nick Coghlan wrote:
On 18 October 2016 at 00:49, Charalampos Stratakis
<cstratak(a)redhat.com> wrote:
> The current URL should be https://beaker.qa.fedoraproject.org/ if that is the one you
have in mind.
Indeed it is, thank you!
Cheers,
Nick.
Hi everyone, I'm observing and chiming in late to this discussion. My
understanding from reading this thread is that it's intended to package
3.6 for Rawhide and eventually having it made as a Change in F26.
If 3.6 is going to be hitting Rawhide, would anyone be interested in
writing an announcement / tips for testing on the Fedora Magazine? I
think this would be a highly-interesting article to our readers to know
that 3.6 is in Rawhide, and there may be some people who are willing to
jump in and help test if they knew the opportunity was there.
Thanks everyone!
--
Cheers,
Justin W. Flory
jflory7(a)gmail.com
10:37 a.m.
Hi,
It would be certainly interesting to write an article about it.
Ideally it remains to be seen which version of python 3.6 is going to be deployed in
rawhide and after deploying it, publish the article so people can do some early testing.
Regards,
Charalampos Stratakis
Associate Software Engineer
Python Maintenance Team, Red Hat
----- Original Message -----
From: "Justin W. Flory" <jflory7(a)gmail.com>
To: python-devel(a)lists.fedoraproject.org
Sent: Friday, October 28, 2016 12:53:49 AM
Subject: Re: Python 3.6 beta release in F26 Rawhide?
On 10/17/2016 10:57 AM, Nick Coghlan wrote:
On 18 October 2016 at 00:49, Charalampos Stratakis
<cstratak(a)redhat.com> wrote:
> The current URL should be https://beaker.qa.fedoraproject.org/ if that is the one you
have in mind.
Indeed it is, thank you!
Cheers,
Nick.
Hi everyone, I'm observing and chiming in late to this discussion. My
understanding from reading this thread is that it's intended to package
3.6 for Rawhide and eventually having it made as a Change in F26.
If 3.6 is going to be hitting Rawhide, would anyone be interested in
writing an announcement / tips for testing on the Fedora Magazine? I
think this would be a highly-interesting article to our readers to know
that 3.6 is in Rawhide, and there may be some people who are willing to
jump in and help test if they knew the opportunity was there.
Thanks everyone!
--
Cheers,
Justin W. Flory
jflory7(a)gmail.com
_______________________________________________
python-devel mailing list -- python-devel(a)lists.fedoraproject.org
To unsubscribe send an email to python-devel-leave(a)lists.fedoraproject.org
12:25 p.m.
Third beta is at copr [0]
[0] https://copr.fedorainfracloud.org/coprs/cstratak/python-3.6/build/472123/
Regards,
Charalampos Stratakis
Associate Software Engineer
Python Maintenance Team, Red Hat
----- Original Message -----
From: "Nick Coghlan" <ncoghlan(a)gmail.com>
To: "Fedora Python SIG" <python-devel(a)lists.fedoraproject.org>
Sent: Monday, October 17, 2016 4:57:09 PM
Subject: Re: Python 3.6 beta release in F26 Rawhide?
On 18 October 2016 at 00:49, Charalampos Stratakis <cstratak(a)redhat.com> wrote:
The current URL should be https://beaker.qa.fedoraproject.org/ if
that is the one you have in mind.
Indeed it is, thank you!
Cheers,
Nick.
--
Nick Coghlan | ncoghlan(a)gmail.com | Brisbane, Australia
_______________________________________________
python-devel mailing list -- python-devel(a)lists.fedoraproject.org
To unsubscribe send an email to python-devel-leave(a)lists.fedoraproject.org
11:16 a.m.
And FESCo ticket about that[0]
[0] https://pagure.io/fesco/issue/1642
Regards,
Charalampos Stratakis
Associate Software Engineer
Python Maintenance Team, Red Hat
----- Original Message -----
From: "Nick Coghlan" <ncoghlan(a)gmail.com>
To: "Fedora Python SIG" <python-devel(a)lists.fedoraproject.org>
Sent: Wednesday, October 12, 2016 8:29:04 AM
Subject: Python 3.6 beta release in F26 Rawhide?
Hi folks,
During the discussion of the os.urandom() change in Python 3.6 (the
successor to the accidental change in Python 3.5 that is the subject
of Tomas's emailing about rebasing to 3.5.2 in F24), we came to the
conclusion it would be good to get 3.6 into Rawhide early enough to
impact the upstream beta cycle:
https://lists.fedorahosted.org/archives/list/python-devel@lists.fedorapro...
However, there's no reference to that discussion in
https://fedoraproject.org/wiki/Changes/Python3.6 - it only refers to
incorporating a release candidate or the actual release, which will be
too late for us to request changes to the upstream default
os.urandom() behaviour if we find unexpected problems with it.
With Python 3.6b2 recently pushed out the door, there's about two
months (including two more beta releases) until the first release
candidate in early December.
Regards,
Nick.
--
Nick Coghlan | ncoghlan(a)gmail.com | Brisbane, Australia
_______________________________________________
python-devel mailing list -- python-devel(a)lists.fedoraproject.org
To unsubscribe send an email to python-devel-leave(a)lists.fedoraproject.org
1:44 p.m.
On 11/01/2016 11:37 AM, Charalampos Stratakis wrote:
Hi,
It would be certainly interesting to write an article about it.
Ideally it remains to be seen which version of python 3.6 is going to be deployed in
rawhide and after deploying it, publish the article so people can do some early testing.
Regards,
Charalampos Stratakis
Associate Software Engineer
Python Maintenance Team, Red Hat
Whoops, missed this reply! Even if the specific minor version of 3.6 is
to be determined, if there's new major features to highlight in Python
3.6, we could get started with writing the article draft and write how
to get started using it. Once it's actually available, we can
double-check for accuracy and push it out quickly after it's available. :)
Would there be anyone who might be interested in helping lead on this?
It shouldn't have to be too extravagant, but a short overview and
introduction about the latest and greatest in Python on Fedora would be
amazing.
I'm also CCing the Magazine list on this reply to help keep them in on
the loop of things too.
----- Original Message -----
From: "Justin W. Flory" <jflory7(a)gmail.com>
To: python-devel(a)lists.fedoraproject.org
Sent: Friday, October 28, 2016 12:53:49 AM
Subject: Re: Python 3.6 beta release in F26 Rawhide?
On 10/17/2016 10:57 AM, Nick Coghlan wrote:
> On 18 October 2016 at 00:49, Charalampos Stratakis <cstratak(a)redhat.com>
wrote:
>> The current URL should be https://beaker.qa.fedoraproject.org/ if that is the one
you have in mind.
>
> Indeed it is, thank you!
>
> Cheers,
> Nick.
>
Hi everyone, I'm observing and chiming in late to this discussion. My
understanding from reading this thread is that it's intended to package
3.6 for Rawhide and eventually having it made as a Change in F26.
If 3.6 is going to be hitting Rawhide, would anyone be interested in
writing an announcement / tips for testing on the Fedora Magazine? I
think this would be a highly-interesting article to our readers to know
that 3.6 is in Rawhide, and there may be some people who are willing to
jump in and help test if they knew the opportunity was there.
Thanks everyone!
--
Cheers,
Justin W. Flory
jflory7(a)gmail.com
7:40 a.m.
On 4 November 2016 at 02:16, Charalampos Stratakis <cstratak(a)redhat.com> wrote:
And FESCo ticket about that[0]
[0] https://pagure.io/fesco/issue/1642
Awesome, thanks for tackling this.
Cheers,
Nick.
--
Nick Coghlan | ncoghlan(a)gmail.com | Brisbane, Australia
8:56 a.m.
On 4 November 2016 at 04:44, Justin W. Flory <jflory7(a)gmail.com> wrote:
Whoops, missed this reply! Even if the specific minor version of 3.6
is to
be determined, if there's new major features to highlight in Python 3.6, we
could get started with writing the article draft and write how to get
started using it. Once it's actually available, we can double-check for
accuracy and push it out quickly after it's available. :)
Would there be anyone who might be interested in helping lead on this? It
shouldn't have to be too extravagant, but a short overview and introduction
about the latest and greatest in Python on Fedora would be amazing.
Some initial highlights from
https://docs.python.org/dev/whatsnew/3.6.html for folks that can just
roll forward to the new release:
- compile time processing of format strings with the new f-string
literals: print(f"There were {len(docs)} found. First title:
{docs[0].title}". These have the dual benefit of being both faster
than runtime formatting (since the string gets broken up into text
segments and field expressions at compile time, so there's zero
runtime string parsing overhead), while also being easier to read
(since you don't need to mentally map expressions to their
corresponding fields - they're right there in the string). Especially
helpful for scripting use cases.
- keyword arguments now preserve their order, so
"collections.OrderedDict(first=1, second=2, third=2)" finally works
the way you would expect it to work (previously the apparent key order
in the source code would be lost in the process of calling the
constructor)
- the new secrets module provides handy helpers for secure token
generation in various formats (e.g. bytes, hex strings, base64
strings) with a reasonable default amount of entropy
- underscores in numeric literals mean you can now break up magic
constants to make them easier to read (e.g. 10_000_000.0, 0xCAFE_F00D,
0b_0011_1111_0100_1110)
- many more standard library APIs, including the builtin open(), now
support pathlib.Path and pathlib.PurePath objects through the new
os.fspath() protocol. This change also means many third party
libraries will also indirectly gain support for these protocols (since
they implicitly delegate the task of opening a path to a standard
library API
- OpenSSL 1.1.0 is supported, along with additional hashing (BLAKE2,
SHA-3, SHAKE) and key derivation (scrypt) algorithms
From a security perspective, os.urandom() now also provides a
guarantee that it will either block or return a result suitable for
cryptographic use - this means that code that needs to run when the
system entropy pool hasn't been initialised yet should either switch
to using the random module (if it doesn't need cryptographic grade
randomness) or the new os.getrandom() API (in order to use the
non-blocking variant of the syscall).
For folks using the new native async/await syntax for coroutine based
service development, that syntax has been extended with provisional
support for asynchronous comprehensions, generator definitions, and
generation functions, allowing asynchronous code access to many more
of the niceties developers are accustomed to when working with purely
synchronous code.
For folks using mypy or one of the other type inference engines for
Python, provisional support has been added for declarative variable
annotations that allow inference engines to complain when values bound
to the variable don't abide by the expected constraint (the
interpreter itself pays no attention to these annotations at runtime,
just as it doesn't check function annotations)
For folks writing internationalised applications, the Unicode database
has been updated to 9.0.0
For folks debugging more complex applications, the new PYTHONMALLOC
environment variable lets you either switch the runtime's memory
allocator into debug mode ("PYTHONMALLOC=debug") or bypass it entirely
("PYTHONMALLOC=malloc"). Details in
https://docs.python.org/dev/whatsnew/3.6.html#pythonmalloc-environment-va...
Also related to application debugging, the "-X tracemalloc" option now
provides a resource allocation traceback when printing ResourceWarning
for resources that are cleaned up non-deterministically.
There have also been a range of performance improvement made to
CPython, aided significantly by Victor Stinner's work in putting
together a new benchmarking utility ("perf") and a new benchmark suite
for Python interpreters ("performance":
https://pypi.python.org/pypi/performance ). (He doesn't have 3.5 vs
3.6 performance data yet, but hopefully that will be available on
speed.python.org by the time of the actual 3.6 release in December)
Cheers,
Nick.
--
Nick Coghlan | ncoghlan(a)gmail.com | Brisbane, Australia
2:40 a.m.
On 11/06/2016 09:56 AM, Nick Coghlan wrote:
On 4 November 2016 at 04:44, Justin W. Flory
<jflory7(a)gmail.com> wrote:
> Whoops, missed this reply! Even if the specific minor version of 3.6 is to
> be determined, if there's new major features to highlight in Python 3.6, we
> could get started with writing the article draft and write how to get
> started using it. Once it's actually available, we can double-check for
> accuracy and push it out quickly after it's available. :)
>
> Would there be anyone who might be interested in helping lead on this? It
> shouldn't have to be too extravagant, but a short overview and introduction
> about the latest and greatest in Python on Fedora would be amazing.
Some initial highlights from
https://docs.python.org/dev/whatsnew/3.6.html for folks that can just
roll forward to the new release:
- compile time processing of format strings with the new f-string
literals: print(f"There were {len(docs)} found. First title:
{docs[0].title}". These have the dual benefit of being both faster
than runtime formatting (since the string gets broken up into text
segments and field expressions at compile time, so there's zero
runtime string parsing overhead), while also being easier to read
(since you don't need to mentally map expressions to their
corresponding fields - they're right there in the string). Especially
helpful for scripting use cases.
- keyword arguments now preserve their order, so
"collections.OrderedDict(first=1, second=2, third=2)" finally works
the way you would expect it to work (previously the apparent key order
in the source code would be lost in the process of calling the
constructor)
- the new secrets module provides handy helpers for secure token
generation in various formats (e.g. bytes, hex strings, base64
strings) with a reasonable default amount of entropy
- underscores in numeric literals mean you can now break up magic
constants to make them easier to read (e.g. 10_000_000.0, 0xCAFE_F00D,
0b_0011_1111_0100_1110)
- many more standard library APIs, including the builtin open(), now
support pathlib.Path and pathlib.PurePath objects through the new
os.fspath() protocol. This change also means many third party
libraries will also indirectly gain support for these protocols (since
they implicitly delegate the task of opening a path to a standard
library API
- OpenSSL 1.1.0 is supported, along with additional hashing (BLAKE2,
SHA-3, SHAKE) and key derivation (scrypt) algorithms
From a security perspective, os.urandom() now also provides a
guarantee that it will either block or return a result suitable for
cryptographic use - this means that code that needs to run when the
system entropy pool hasn't been initialised yet should either switch
to using the random module (if it doesn't need cryptographic grade
randomness) or the new os.getrandom() API (in order to use the
non-blocking variant of the syscall).
For folks using the new native async/await syntax for coroutine based
service development, that syntax has been extended with provisional
support for asynchronous comprehensions, generator definitions, and
generation functions, allowing asynchronous code access to many more
of the niceties developers are accustomed to when working with purely
synchronous code.
For folks using mypy or one of the other type inference engines for
Python, provisional support has been added for declarative variable
annotations that allow inference engines to complain when values bound
to the variable don't abide by the expected constraint (the
interpreter itself pays no attention to these annotations at runtime,
just as it doesn't check function annotations)
For folks writing internationalised applications, the Unicode database
has been updated to 9.0.0
For folks debugging more complex applications, the new PYTHONMALLOC
environment variable lets you either switch the runtime's memory
allocator into debug mode ("PYTHONMALLOC=debug") or bypass it entirely
("PYTHONMALLOC=malloc"). Details in
https://docs.python.org/dev/whatsnew/3.6.html#pythonmalloc-environment-va...
Also related to application debugging, the "-X tracemalloc" option now
provides a resource allocation traceback when printing ResourceWarning
for resources that are cleaned up non-deterministically.
There have also been a range of performance improvement made to
CPython, aided significantly by Victor Stinner's work in putting
together a new benchmarking utility ("perf") and a new benchmark suite
for Python interpreters ("performance":
https://pypi.python.org/pypi/performance ). (He doesn't have 3.5 vs
3.6 performance data yet, but hopefully that will be available on
speed.python.org by the time of the actual 3.6 release in December)
Cheers,
Nick.
Thanks for all of this info, Nick! I think we could get this down into a
nice and tidy Magazine article. Would you be able to try creating a
draft in the Magazine and we can work through the rest of the steps from
there? This would be an awesome article to have!
https://fedoramagazine.org/writing-an-article-for-the-fedora-magazine/
--
Cheers,
Justin W. Flory
jflory7(a)gmail.com
2737
days inactive
2766
days old
python-devel@lists.fedoraproject.org
14 comments
3 participants
participants (3)
-
Charalampos Stratakis -
Justin W. Flory -
Nick Coghlan