[python-committers] Re: Cleaning up the historical list of core developers

[Alexandre Vassalotti]

On Thu, Jul 4, 2019 at 5:00 AM Antoine Pitrou  wrote:

> > So, how do we pull together a clean-enough list of historical core
> > developers? Here is my idea of criteria of people to be on the list
> > (based on the developer log and the git log):
> >
> >   * Was not a GSoC student (clarification to follow for those who fall
> > into this category and are actually active)
>
> I think you should replace "are actually active" with "have been
> actually active after their GSoC project" (without necessary being
> active *now*).  Example with Alexandre, who's been the pickle maintainer
> during several years but is inactive now:
>

Oh, I'm not inactive (at least not by the definition in PEP 13
.) I was part of the
initial active core team members who were grandfathered in from the "Python
core" team on GitHub, and nobody asked me to declare myself as inactive
(yet!) But outside of the PEP 13 definition, yeah, it is true that I am not
actively contributing right now. (I still read the mailing lists and still
keep an eye on the pickle module though.) I would be sad to see my
membership invalidated because I became a committer through GSoC.

And BTW, PEP 13 defined the initial inactive members as anyone who has been
a committer in the past. PEP 13 didn't qualify the membership on what
process the person went through become a committer (e.g., by a vote, for
GSoC, or for sprints). Brett, are you planning to propose an amendment to
PEP 13 to change that?

-- Alexandre
___
python-committers mailing list -- python-committers@python.org
To unsubscribe send an email to python-committers-le...@python.org
https://mail.python.org/mailman3/lists/python-committers.python.org/
Message archived at 
https://mail.python.org/archives/list/python-committers@python.org/message/4XHI4RYZ6IYLYCNFKGKLTKW2EFRMSVFK/
Code of Conduct: https://www.python.org/psf/codeofconduct/

[python-committers] Re: Python Core Developer Status Inquiry

[Alexandre Vassalotti]

Hi Marc-Andre,

I updated my status in the github file directly. Why am I still being
listed here?

-- Alexandre

On Wed, Nov 18, 2020 at 7:44 AM M.-A. Lemburg  wrote:

> I've sent a reminder to these core devs:
>
>  Alexandre Vassalotti
>  Amaury Forgeot d'Arc
>  Armin Ronacher
>  David Wolever
>  Eli Bendersky
>  Jack Diederich
>  Jack Jansen
>  Jeremy Hylton
>  Kurt B. Kaiser
>  Lars Gustäbel
>  Martin Panter
>  Matthias Klose
>  Meador Inge
>  PJ Eby
>  Philip Jenvey
>  Sjoerd Mullender
>  Steven D'Aprano
>  Thomas Heller
>  Trent Nelson
>
> who have not replied yet.
>
> The deadline is Nov 25 AoE, when I'll merge the PR with the updates:
> https://github.com/python/voters/pull/30
>
> Thanks.
>
> On 11.11.2020 22:00, M.-A. Lemburg wrote:
> > FYI: I have sent out the Python Code Developer status inquiries to
> > these core developers, which have not committed to the CPython
> > Github repo in the last two years and for which we don't have
> > a status answer using the new inactivity reply feature in the
> > voter roll script yet:
> >
> >  Alex Martelli
> >  Alexandre Vassalotti
> >  Amaury Forgeot d'Arc
> >  Armin Ronacher
> >  Christian Tismer
> >  David Malcolm
> >  David Wolever
> >  Doug Hellmann
> >  Eli Bendersky
> >  Fred Drake
> >  Georg Brandl
> >  Hynek Schlawack
> >  Jack Diederich
> >  Jack Jansen
> >  Jeremy Hylton
> >  Kurt B. Kaiser
> >  Lars Gustäbel
> >  Marc-André Lemburg
> >  Mark Hammond
> >  Martin Panter
> >  Matthias Klose
> >  Meador Inge
> >  PJ Eby
> >  Petri Lehtinen
> >  Philip Jenvey
> >  Sandro Tosi
> >  Sjoerd Mullender
> >  Steven D'Aprano
> >  Thomas Heller
> >  Tim Golden
> >  Trent Nelson
> >
> > For some more background, please have a look at the ticket
> > https://github.com/python/voters/issues/16 and the associated
> > PR https://github.com/python/voters/pull/25
> >
> > I used the email addresses from the python-core.toml file and
> > will collect replies in the next two weeks and collect them
> > in this PR: https://github.com/python/voters/pull/30
> > This can then be merged before creating the final voter roll
> > for the election.
> >
> > PS: I attached the mail merge template I used for the emails below.
> >
> > Cheers,
> >
> >
> > ___
> > python-committers mailing list -- python-committers@python.org
> > To unsubscribe send an email to python-committers-le...@python.org
> > https://mail.python.org/mailman3/lists/python-committers.python.org/
> > Message archived at
> https://mail.python.org/archives/list/python-committers@python.org/message/O3CC7U2ERJLUCJRE7UOE7GIXME5VK3LL/
> > Code of Conduct: https://www.python.org/psf/codeofconduct/
> >
>
> --
> Marc-Andre Lemburg
> eGenix.com
>
> Professional Python Services directly from the Experts (#1, Nov 18 2020)
> >>> Python Projects, Coaching and Support ...https://www.egenix.com/
> >>> Python Product Development ...https://consulting.egenix.com/
> 
>
> ::: We implement business ideas - efficiently in both time and costs :::
>
>eGenix.com Software, Skills and Services GmbH  Pastor-Loeh-Str.48
> D-40764 Langenfeld, Germany. CEO Dipl.-Math. Marc-Andre Lemburg
>Registered at Amtsgericht Duesseldorf: HRB 46611
>https://www.egenix.com/company/contact/
>  https://www.malemburg.com/
> ___
> python-committers mailing list -- python-committers@python.org
> To unsubscribe send an email to python-committers-le...@python.org
> https://mail.python.org/mailman3/lists/python-committers.python.org/
> Message archived at
> https://mail.python.org/archives/list/python-committers@python.org/message/4IF2GAKPJSZWCDRQUDDVHULGLU4TDDDQ/
> Code of Conduct: https://www.python.org/psf/codeofconduct/
>
___
python-committers mailing list -- python-committers@python.org
To unsubscribe send an email to python-committers-le...@python.org
https://mail.python.org/mailman3/lists/python-committers.python.org/
Message archived at 
https://mail.python.org/archives/list/python-committers@python.org/message/OCNA5L5HYYZYYX4G5BIUTMXKZ6EJSMZQ/
Code of Conduct: https://www.python.org/psf/codeofconduct/

Re: [python-committers] ubuntu release plan

[Alexandre Vassalotti]

On Fri, Aug 15, 2008 at 4:42 AM, Christian Heimes <[EMAIL PROTECTED]> wrote:
> I blindly assume that non of us is going to say "Give me bucks or I won't
> code any more". But our economy is going through a recession, everything is
> getting more expensive by the day. A constant income would allow some guys
> to code without them worrying about money.
> For example we have several talented students in our midst. Let's tap into
> their potential by hiring them. They could use their talent to our benefits
> instead of earning money through internships or side jobs.

To me, that sounds much like Google Summer of Code, except with more
weight on the hiree's shoulders to perform well. The main difference
would probably be that a PSF sponsored developer wouldn't be focused
on a single project.

-- Alexandre
___
python-committers mailing list
python-committers@python.org
http://mail.python.org/mailman/listinfo/python-committers

Re: [python-committers] Luke Kenneth

[Alexandre Vassalotti]

On Sun, Jan 25, 2009 at 2:18 PM, "Martin v. Löwis"  wrote:
>> Anyone who feels like biting his head off, go for it.
>
> I think as a starting point, I'll revoke his access to the tracker
> (although I guess he'll create a new account in response).
>

Well. Maybe, it would be better to first explain him that he disturbs
the project and to ask him nicely to stop. If that fails, then go
ahead with the less friendly approach.

-- Alexandre
___
python-committers mailing list
python-committers@python.org
http://mail.python.org/mailman/listinfo/python-committers

Re: [python-committers] I've got a surprise for you!

[Alexandre Vassalotti]

[SNIP: Trent announces his awesome secret project]

There is only one word I can say: wow! And to everyone who was
involved, thank you!

This massive buildbot network is really going to help us toward making
Python a top-class platform in term of portability. I am sure that
having SSH access to the buildbots will encourage everyone to fix bugs
quickly.

Finally, I have one question. Will these buildbots be open for general
development work? It would be great to have access to them for
creating new cross-platform libraries for Python.

-- Alexandre
___
python-committers mailing list
python-committers@python.org
http://mail.python.org/mailman/listinfo/python-committers

Re: [python-committers] Data corruption issue (C IO library)

[Alexandre Vassalotti]

On Thu, Aug 6, 2009 at 7:28 PM, Georg Brandl wrote:
> Antoine Pitrou schrieb:
>> Hello,
>>
>> A data corruption issue has been discovered in the C IO lib in Python
>> 3.1 (http://bugs.python.org/issue6629). I've applied a fix, and I wonder
>> whether we should make a release quickly to minimize the probability of
>> users hitting the problem?
>> (Georg tells me Benjamin is on holiday, however)
>
> FWIW, I also think we should make a new micro release right now.  We can't
> be seen to take data corruption issues with the most basic file operations
> lightly, especially in Python 3; otherwise, people will think we still don't
> consider it ready for use.

+1 for a micro release.

-- Alexandre
___
python-committers mailing list
python-committers@python.org
http://mail.python.org/mailman/listinfo/python-committers

Re: [python-committers] Misc/NEWS entries added to released versions

[Alexandre Vassalotti]

On Mon, Sep 14, 2009 at 10:05 AM, R. David Murray  wrote:
> But the problem we are trying to solve is the fact that the NEWS
> entries wind up in the _wrong_ section on merges.  Any thoughts
> about how to solve that under Mercurial?
>

Could we add a version tag to each NEWS entry? Or perhaps, we could
move the content of NEWS to NEWS.history after each release? These may
not be the most elegant solutions, but I think either would solve the
issue.

-- Alexandre
___
python-committers mailing list
python-committers@python.org
http://mail.python.org/mailman/listinfo/python-committers

Re: [python-committers] SSH keys and Keychain

[Alexandre Vassalotti]

On Wed, Mar 3, 2010 at 5:32 PM, Vinay Sajip  wrote:
> I've installed Keychain and invoked it in my .bashrc, and whenever I open a
> terminal session, it tells me that it found an existing ssh-agent and the
> SSH_AUTH_SOCK and SSH_AGENT_PID seem to be correct.

Are you using Ubuntu? If so, Seahorse (the default key manager in
Ubuntu) should prompt you automatically for your passphrase and cache
it.  Keychain might be interfering with it, so try to uninstall it
first. Then verify in Applications → Accessories → Passwords and
Encryption Keys that Seahorse sees your SSH key.

I hope that helps,

-- Alexandre
___
python-committers mailing list
python-committers@python.org
http://mail.python.org/mailman/listinfo/python-committers

Re: [python-committers] svnmerge init on py3k branch fails..

[Alexandre Vassalotti]

On Tue, Mar 23, 2010 at 11:13 AM, Nick Coghlan  wrote:
> I'm not sure if there should be any change in the wording of the FAQ
> entry for this - maybe expanding on the last sentence a bit?
>

Could we put a commit hook to prevent committing unintentional
"svnmerge.py init"?

-- Alexandre
___
python-committers mailing list
python-committers@python.org
http://mail.python.org/mailman/listinfo/python-committers

Re: [python-committers] Untabifying the C codebase

[Alexandre Vassalotti]

On Sun, May 9, 2010 at 6:01 PM, A.M. Kuchling  wrote:
> I'm happy to see the curses module re-indented.  Does anyone have a
> set of settings for Emacs or for GNU indent for Python's C indentation
> style?
>

This invocation of GNU indent should work reasonably well:

indent \
  --no-tabs \
  --indent-level8 \
  --blank-lines-after-procedures \
  --no-blank-lines-after-declarations \
  --no-comment-delimiters-on-blank-lines \
  --start-left-side-of-comments \
  --braces-on-if-line \
  --dont-cuddle-else \
  --cuddle-do-while \
  --case-indentation0 \
  --dont-space-special-semicolon \
  --no-space-after-function-call-names \
  --space-after-for \
  --space-after-if \
  --space-after-while \
  --no-blank-lines-after-commas \
  --declaration-indentation1 \
  --braces-on-struct-decl-line \
  --procnames-start-lines \
  --continue-at-parentheses \
  --preprocessor-indentation0 \
  --break-after-boolean-operator

-- Alexandre
___
python-committers mailing list
python-committers@python.org
http://mail.python.org/mailman/listinfo/python-committers

Re: [python-committers] New committer proposal: Alexander Belopolsky

[Alexandre Vassalotti]

+1

-- Alexandre

On Thu, May 20, 2010 at 1:28 PM, Mark Dickinson  wrote:
> I propose that Alexander Belopolsky be given svn commit access.  I've
> already checked with him that he's interested (he is), and I'm
> prepared to mentor him while he's learning the ropes.
>
> A brief history: Alexander's been contributing patches for almost
> seven years (I think http://bugs.python.org/issue798269 is the first);
> in that time he's provided numerous patches, comments, and patch
> reviews.  Just as a guide, a quick search on bugs.python.org shows
> that he's nosy on over 200 issues.  I've recently worked closely with
> him on a couple of patches, and think he's ready for commit rights.
>
> In particular, I think it would be great to have his help with the
> datetime module, which is in currently need of some care and
> attention.
>
> Any objections or comments?
>
> Mark
___
python-committers mailing list
python-committers@python.org
http://mail.python.org/mailman/listinfo/python-committers

Re: [python-committers] Contributor agreement for GSoC2012

[Alexandre Vassalotti]

On Tue, Jun 26, 2012 at 10:56 AM, Pat Campbell  wrote:

> In order for me to add your contributor agreement form to your profile (on
> the online bug
> tracker) I will need to access your user number webpage or please provide
> the link to your
>
> "user# editing" webpage in order for me to mark (Yes) to receiving your
> contributor
> agreement form.
>


Hi Pat,

This is Stefan's user page: http://bugs.python.org/user16149
___
python-committers mailing list
python-committers@python.org
http://mail.python.org/mailman/listinfo/python-committers

[python-committers] Django running in debug mode on bugs.python.org

[Alexandre Vassalotti]

Hi guys,

I just got an exception from the code review tool running on bugs.python.org.
The server returned the full debug stack trace (which means DEBUG=True in
Django). Is this intended?

Cheers,
-- Alexandre
___
python-committers mailing list
python-committers@python.org
http://mail.python.org/mailman/listinfo/python-committers