Starting with core-mentorship and then core-workflow sounds good.
Let me first find out what it's going to take to do the migration. (I
actually have no idea!)
I've sent an email to postmaster and asked for more details :)
Hope it's not too complicated...
Mariatta Wijaya
Another one is core-mentorship, which satisfies the same criteria; and in
my view this has the added and useful property that its beneficiaries are
non-core members. After that I'd do core-workflow. Honestly I'd leave
python-committers alone for a while, we're a curmudgeonly group. :-)
On Wed, Nov
+1 committers
> On Nov 1, 2017, at 7:54 PM, Barry Warsaw wrote:
>
> On Nov 1, 2017, at 19:42, Guido van Rossum wrote:
>>
>> Maybe we should try it on some other list too? I know it works "in
>> principle" and I'd love for all Python mailing lists to migrate, but I'd
>> like to have some more
On Nov 1, 2017, at 19:42, Guido van Rossum wrote:
>
> Maybe we should try it on some other list too? I know it works "in principle"
> and I'd love for all Python mailing lists to migrate, but I'd like to have
> some more experience with community mailing lists before tackling python-dev.
What
Maybe we should try it on some other list too? I know it works "in
principle" and I'd love for all Python mailing lists to migrate, but I'd
like to have some more experience with community mailing lists before
tackling python-dev.
On Wed, Nov 1, 2017 at 7:31 PM, Barry Warsaw wrote:
> On Nov 1, 2
On Nov 1, 2017, at 18:49, Mariatta Wijaya wrote:
>
> Anything I can do to help make the migration to MM3 + HyperKitty happen? :)
Thanks for the offer Mariatta! Assuming this is something we want to go
through with, probably the best way to get there is to work with the
postmaster, especially
Thiebaud:
Thank you. I have started discussions within Intel for updating the UEFI
CPython implementation to Python 3.x. The TianoCore community would appreciate
contributions by people with Python experience to bring this code up to current
standards.
Please review the contribution guidelines
On 2 November 2017 at 09:16, Lukasz Langa wrote:
> I find this sad. In the JavaScript community the existence of Babel is
> very important for the long-term evolution of the language independently
> from the runtime. With Babel, JavaScript programmers can utilize new
> language syntax while being
Anything I can do to help make the migration to MM3 + HyperKitty happen? :)
Mariatta Wijaya
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
https://mail.python.org/mailman/options/python
On 2 November 2017 at 07:47, Ned Deily wrote:
> Happy belated Halloween to those who celebrate it; I hope it wasn't too
> scary! Also possibly scary: we have just a little over 12 weeks remaining
> until Python 3.7's feature code cutoff, 2018-01-29. Those 12 weeks include
> a number of traditio
> On Oct 30, 2017, at 4:00 AM, Victor Stinner wrote:
>
> Except of Antoine Pitrou, does everybody else like the new UI? :-)
I also much prefer MM3 and HyperKitty.
The old pipermail tree looks more inviting (I like the concise tree) but it's
deceiving. When you actually start going through an
The original poster is an elementary school student. To keep the list clean, I
responded 1:1 in a more inviting manner. Hopefully the person will succeed
installing and learning Python :-)
- Ł
> On Oct 28, 2017, at 2:33 PM, Terry Reedy wrote:
>
> On 10/27/2017 4:43 PM, London wrote:
>> can yo
I find this sad. In the JavaScript community the existence of Babel is very
important for the long-term evolution of the language independently from the
runtime. With Babel, JavaScript programmers can utilize new language syntax
while being able to deploy on dated browsers. While there's always
Based on positive feedback on python-ideas back in September,
I'm publishing the second draft for consideration on python-dev.
I hope you like it!
A nicely formatted rendering is available here:
https://www.python.org/dev/peps/pep-0563/
(Just make sure you're looking at the version that has
"Post
Happy belated Halloween to those who celebrate it; I hope it wasn't too scary!
Also possibly scary: we have just a little over 12 weeks remaining until Python
3.7's feature code cutoff, 2018-01-29. Those 12 weeks include a number of
traditional holidays around the world so, if you are planning
The official guidelines on what it takes to add official support for a
platform is https://www.python.org/dev/peps/pep-0011/#supporting-platforms.
Basically it's a core dev willing to sponsor and maintain the work, a
buildbot, and implicitly at least a 5 year commitment.
On Wed, 1 Nov 2017 at 05:5
Hi python-dev,
It's been over a month without any activity and over a week since my ping,
and I'm still waiting for a review on my pull request:
https://bugs.python.org/issue30140
https://github.com/python/cpython/pull/1325
I would greatly appreciate if someone has time to take a look. This is my
Hi,
UEFI has become the standard for firmware (BIOS) interface. Intel has
provided an open source implementation under the name EDK2 (part of
the TianoCore initiative) [1] for some time. This implementation has
evolved significantly and now provides the functionalities of a small
OS with a standar
On Wed, 1 Nov 2017 13:46:27 +0100
Christian Heimes wrote:
>
> > This work would target the master branch (that is Python 3). I would
> > be interested in hearing your thoughts on this idea.
>
> In general your proposal sounds like a good idea. A new platform may
> require a PEP, though.
It wo
On 2017-11-01 10:07, Thiebaud Weksteen wrote:
> Hi,
>
> UEFI has become the standard for firmware (BIOS) interface. Intel has
> provided an open source implementation under the name EDK2 (part of
> the TianoCore initiative) [1] for some time. This implementation has
> evolved significantly and now
20 matches
Mail list logo
