On Sun, Jul 28, 2019 at 1:25 PM Antoine Pitrou wrote:
> On Fri, 26 Jul 2019 19:09:35 -0700
> Guido van Rossum wrote:
> > See the thread 'The trouble with "Easy" issues' in
> > core-mentors...@python.org.
> > Essentially those "easy" issues
t targets?
>
> Skip
>
>
> Skip
> ___
> Python-Dev mailing list -- python-...@python.org
> To unsubscribe send an email to python-dev-le...@python.org
> https://mail.python.org/mailman3/lists/python-dev.python.org/
> Message
mailing list -- core-workflow@python.org
> To unsubscribe send an email to core-workflow-le...@python.org
> https://mail.python.org/mm3/mailman3/lists/core-workflow.python.org/
> This list is governed by the PSF Code of Conduct:
> https://www.python.org/psf/codeofconduct
>
--
--Guid
iki/Minneapolis–Saint_Paul_International_Airport> I
> assume.
>
See also: https://xkcd.com/1937/
--
--Guido van Rossum (python.org/~guido)
___
core-workflow mailing list -- core-workflow@python.org
To unsubscribe send an email to core-work
n't know you but you wanted to get involved at the
> admin-level).
>
> ___
> core-workflow mailing list -- core-workflow@python.org
> To unsubscribe send an email to core-workflow-le...@python.org
> https://mail.python.org/mm3/mailman3/l
at 06:23, Guido van Rossum <gu...@python.org> wrote:
> > I've also got confirmation from Tim Abbott (ZulipChat cofounder) that
> they'd
> > be happy to host us and would even prioritize features they want.
>
> Cool - I've mainly been exposed to the Zulip community
ith an
> experiment,
> > and it would be good to create a plan for evaluating success. If you
> want to
> > help out, please volunteer to write up such a plan -- implementation
> will be
> > easy.
>
> I would like to help out with this although I am really new
t; ___
> core-workflow mailing list -- core-workflow@python.org
> To unsubscribe send an email to core-workflow-le...@python.org
> https://mail.python.org/mm3/mailman3/lists/core-workflow.python.org/
> This list is governed by the PSF Code of Co
it's easy and quick enough.
>
If you have the right permissions on the AppVeyor project there are buttons
to create a new build and to re-build a pr:
https://www.dropbox.com/s/bm9zs21bn5af11b/Screenshot%202018-02-25%2019.13.47.png?dl=0
--
--Guido van Rossum (python.org/~guido)
___
python.org/psf/codeofconduct
> ___
> core-workflow mailing list -- core-workflow@python.org
> To unsubscribe send an email to core-workflow-le...@python.org
> https://mail.python.org/mm3/mailman3/list
;
> Cheers,
> Eric
>
> --
> Eric Holscher
> Maker of the internet residing in Portland, Oregon
> http://ericholscher.com
> ___
> core-workflow mailing list
> core-workflow@python.org
> https://mail.python.org/mailman/listinfo/co
at RTD -- the peps and devguide won't cause any load in comparison.
--
--Guido van Rossum (python.org/~guido)
___
core-workflow mailing list
core-workflow@python.org
https://mail.python.org/mailman/listinfo/core-workflow
This list is governed by the PSF
mailing list
> core-workflow@python.org
> https://mail.python.org/mailman/listinfo/core-workflow
> This list is governed by the PSF Code of Conduct:
> https://www.python.org/psf/codeofconduct
>
--
--Guido van Rossum (python.org/~guido)
___
On Tue, Jan 5, 2016 at 12:35 PM, Senthil Kumaran <sent...@uthcode.com>
wrote:
> Are we not going to have 2.7 as a separate repo?
>
Why would you want this?
> I believe, this is possible even if we keep cpython with full history (and
> branches).
>
--
--Guido van Ross
t;
> ___
> core-workflow mailing list
> core-workflow@python.org
> https://mail.python.org/mailman/listinfo/core-workflow
> This list is governed by the PSF Code of Conduct:
> https://www.python.org/psf/codeofconduct
>
--
--Guido
overned by the PSF Code of Conduct:
> https://www.python.org/psf/codeofconduct
> ___
> core-workflow mailing list
> core-workflow@python.org
> https://mail.python.org/mailman/listinfo/core-workflow
> This list is governed by the PSF Code of
er
> should also eliminate most of the clutter from "git log", while still
> presenting the meaningful changes to each branch.
>
> Cheers,
> Nick.
>
> --
> Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia
> ______________
FWIW we use a bot for commits at Dropbox. Its failure doesn't stop everyone
from doing work -- it just prevents a specific commit from going through
automatically (this won't stop other commits from going through). You can
always manually bypass the bot. So I'm not worried about bots much.
On Sat, Dec 12, 2015 at 1:11 PM, Barry Warsaw <ba...@python.org> wrote:
> On Dec 12, 2015, at 09:52 AM, Guido van Rossum wrote:
>
> >Honestly, to cut things short, I think we should go with GitHub and pay
> >them for enterprise support, if they'll take our mon
ter 10+ years of using
web-based review tools I personally wouldn't dream of using a
terminal-based *review* (as opposed to merge) process. Though of course if
that's your preference you should be able to do it.
--
--Guido van Rossum (python.org/~guido)
20 matches
Mail list logo
