Re: [python-committers] [Python-Dev] Reminder: snapshots and releases coming up in the next several days
On Wed, Sep 13, 2017 at 12:35 PM, Ned Deily wrote: > Lots of releases coming up soon! There's a "Python Release Schedule" calendar on Google Calendar that used to be maintained, but that appears to have been dropped, though I found it useful. Is there any sort of calendar feed available with this schedule that's currently maintained? -Fred -- Fred L. Drake, Jr. "A storm broke loose in my mind." --Albert Einstein ___ python-committers mailing list python-committers@python.org https://mail.python.org/mailman/listinfo/python-committers Code of Conduct: https://www.python.org/psf/codeofconduct/
Re: [python-committers] An alternative governance model
> On Jul 18, 2018, at 4:14 PM, Mariatta Wijaya > wrote: > Let's be clear that we're not yet at the stage where we can vote for > anything, let alone how to vote. On Wed, Jul 18, 2018 at 6:03 PM Łukasz Langa wrote: > I don't understand what you mean. Before we get to vote on a variant of PEP > 2, we need to decide how we are supposed to perform that vote. This needs to > be decided before we discuss councils, dictators, and so on because it's all > moot if there is no accepted way to agree which governance model we want. Humans do so love to argue! Both the decision-making process and the candidate decisions are reasonable to discuss; there's no intrinsic ordering constraint for reasonable discussion. We need to decide on the decision-making mechanism before the decision can be made, but that's it. PEP 2 is (currently) the "Procedure for Adding New Modules". Though superseded, recycling the PEP number seems out of character with the RFC process from which we derived the PEP process. Let's be cautious about recycling like that; integers are cheap. -Fred -- Fred L. Drake, Jr. "A storm broke loose in my mind." --Albert Einstein ___ python-committers mailing list python-committers@python.org https://mail.python.org/mailman/listinfo/python-committers Code of Conduct: https://www.python.org/psf/codeofconduct/
Re: [python-committers] An alternative governance model
On Wed, Jul 18, 2018 at 7:16 PM Mariatta Wijaya wrote: > Next available is PEP lucky number 13 🙂 > As an integer, it has no known problems. What could possibly go wrong? ;-) To bad safe, make sure it lands on a Friday. -Fred -- Fred L. Drake, Jr. "A storm broke loose in my mind." --Albert Einstein ___ python-committers mailing list python-committers@python.org https://mail.python.org/mailman/listinfo/python-committers Code of Conduct: https://www.python.org/psf/codeofconduct/
Re: [python-committers] discuss.python.org participation
On Tue, Oct 9, 2018 at 11:25 PM Jack Diederich wrote: > I'm worried about the new format combined with governance discussions. > As best I can tell 51 CPython committers have signed up for an account > [I think that is a big number, btw] but only 17 have posted anything; That > 17 is about 5 more people than put their name on a governance PEP. > And maybe 5 people have half the total posts. This does not feel like a > discussion at all. It can (reasonably) take months for a small-ish group to migrate to a new type of forum; large groups take longer. > I don't think it was deliberate, but it looks like the new format is actively > discouraging everyone but those most deeply invested with the most free time > from participating. I doubt anyone intended to cut anyone out of discussions, but a new medium at this time just wasn't a good idea. It also didn't seem to work well when I first tried to sign up (the round-trip email never came through; yes, I checked my spam-box). Things like this make uptake even slower. -Fred -- Fred L. Drake, Jr. "A storm broke loose in my mind." --Albert Einstein ___ python-committers mailing list python-committers@python.org https://mail.python.org/mailman/listinfo/python-committers Code of Conduct: https://www.python.org/psf/codeofconduct/
[python-committers] Re: Possible bug in voting system ? (was: Re: Reminder to vote for the 2020 Steering Council)
On Wed, Dec 11, 2019 at 2:31 PM Mariatta wrote: > Re: notifying and sending email to people who were marked as inactive by > the script. > We can send automated email via Zapier. Let me know how I can help with > this part. > I think an automated email to the candidates for removal which is very direct about their imminent removal would be sufficiently effective. The difficult part is getting the wording right without sounding like a fire alarm. -Fred -- Fred L. Drake, Jr. "A storm broke loose in my mind." --Albert Einstein ___ 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/LWV33O2HEPXI5E4TH435CEGXDEGHSUL4/ Code of Conduct: https://www.python.org/psf/codeofconduct/
[python-committers] Re: Please make sure you're following good security practices with your GitHub account
On Tue, Jun 15, 2021 at 2:08 PM Mariatta wrote: > Thanks for sharing your experience, and I think it's important for us core > developers to be careful and vigilant about this. > Work picked up hardware fobs from Deepnet Security for a lower price. We paid about $16 apiece for 20, but had to go through their "request a quote" web form. Something like that should work fine for anyone who doesn't want to use a smartphone or bind it to their password manager. (After all, it wouldn't really be 2FA if your password manager provided both factors!) -Fred -- Fred L. Drake, Jr. "There is nothing more uncommon than common sense." --Frank Lloyd Wright ___ 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/JK5PCOF6QPKDYRODB6RNC2H3QAVRAINX/ Code of Conduct: https://www.python.org/psf/codeofconduct/
Re: [python-committers] 3.0rc2 schedule
On Oct 2, 2008, at 8:59 AM, Nick Coghlan wrote: A big +1 from me for declaring it still in beta until all the 3.0 release blockers are fixed. +1 from me as well. From what I've read about the pathname issues, I'm pretty worried about the usability of 3.0. -Fred -- Fred L. Drake, Jr. ___ python-committers mailing list python-committers@python.org http://mail.python.org/mailman/listinfo/python-committers
Re: [python-committers] 3.0rc2 schedule
On Oct 2, 2008, at 9:39 AM, Nick Coghlan wrote: If you don't make a habit of borking your own filesystems with dodgy filenames, it runs fine. I really hope the individuals making this argument are being facetious. I don't think this is the source of the problem at all. The expect the most common occurrence of the problem comes from sharing of drives between operating systems and individual configurations; those ubiquitous little USB "thumb" drives get shared between all kinds of computers these days as people share files they don't want to or can't pass over a network for whatever reason. (Those drives might actually serve other purposes first, such as being music players, and so may have no other interfaces for transferring files.) If someone hands me a USB flash drive with filenames encoded in whatever is reasonable for them, I should be able to use Python tools on the files without having to use non-Python tools to copy or rename the file first. The possibility of a conflicting encoding is increased if the source machine is configured to use a very different encoding, clearly, but that's not that unusual. The world is smaller than it used to be, and we really need to understand that. -Fred -- Fred L. Drake, Jr. ___ python-committers mailing list python-committers@python.org http://mail.python.org/mailman/listinfo/python-committers
Re: [python-committers] 3.0rc2 schedule
On Oct 2, 2008, at 1:53 PM, Guido van Rossum wrote:
we have no choice of coming up with a way of encoding all possible
byte sequences into Unicode strings, using a reversible encoding. This
has been shown to be hard no matter what encoding you favor -- as soon
as those "Unicode" strings are passed on to other libraries or
programs nobody is sure how they will be treated.
Indeed; weird encoding heuristics would be unusable in practice, and
don't seem to offer benefits to those building higher-level
portability layers either. I see no future for that approach.
If we switch to the view that all filenames are bytes after all,
Windows loses, because because not all filenames are representable
that way (unless you deviate from the encoding that Windows has chosen
for you, which presents other problems). Also, it would be a *huge*
project, since filenames are so ubiquitous.
As much as I'd like to say files and paths are bytes ('cause that's
easy), I agree that it doesn't work that way either. Paths are
platform-specific, and Windows and Unix might disagree just for the
principal of the thing for many years to come.
There are a number of ways out, but I don't think we'll be able to
come up with a solution without doing a lot of experimentation.
Therefore I believe the best thing to do is to release 3.0 with a
low-level solution that makes it possible to carry out those
experiments.
Agreed. Having it be possible to use whatever the "right" solution is
on each platform is about as good as it gets in the short term.
Getting good, portable abstractions on top of that will take time.
That doesn't mean it's not scary when thinking about writing portable
code in this environment. That's not entirely new, but the fact that
so much of these details are being addressed so late in the release
cycle *should* give cause for concern, especially to those of use who
are still a long way from stepping up to current versions.
-Fred
--
Fred Drake
___
python-committers mailing list
python-committers@python.org
http://mail.python.org/mailman/listinfo/python-committers
Re: [python-committers] 3.0rc2 schedule
On Oct 2, 2008, at 2:46 PM, Guido van Rossum wrote: It's really not very invasive, and not much changes -- the changes are mostly in our minds, as we now have all learned about the issues and the differences between platforms, and know what to tell people to do about them. *That* is the major change, not the few code changes. Heh. Doesn't pay to educate users, does it? :-/ At about the same time, Martin said: I agree. I disagree that you should be able to do so with Python 3.0 (although it looks like you might). Why do you disagree that I should be able to do this with Python 3.0? (I can guess, but that just increases the likelihood that I'll be wrong, which I don't like.) -Fred -- Fred Drake ___ python-committers mailing list python-committers@python.org http://mail.python.org/mailman/listinfo/python-committers
Re: [python-committers] 3.0rc2 schedule
On Oct 2, 2008, at 3:08 PM, Martin v. Löwis wrote: I'm still in favor of a solution that doesn't divide the APIs into "character file names" and "byte file names"; I want the "character file names" to work always. However, I find it completely unrealistic to make this work in Python 3.0. Ok, that's reasonable. I'm not expecting to be able to use character- file-names everywhere in 3.0, or really anywhere, as nice as that would be. I just want to be able to perform all operations with all files (to the extent they're supported by the O/S and filesystem, etc.). Making a convenient, portable API that lets me do that easily is certainly out of scope. -Fred -- Fred Drake ___ python-committers mailing list python-committers@python.org http://mail.python.org/mailman/listinfo/python-committers
Re: [python-committers] Untabifying the C codebase
On Tue, May 11, 2010 at 9:25 AM, Barry Warsaw wrote: > Who remembers the Great Renaming? :) Oooh! Oooh! I know that one! :-) -Fred -- Fred L. Drake, Jr. "Chaos is the score upon which reality is written." --Henry Miller ___ python-committers mailing list python-committers@python.org http://mail.python.org/mailman/listinfo/python-committers
Re: [python-committers] Untabifying the C codebase
On Tue, May 11, 2010 at 3:20 PM, "Martin v. Löwis" wrote: > Wasn't it the /Grand/ Renaming? Rest assured, the Grand Renaming was a Great and Wondrous Event. -Fred -- Fred L. Drake, Jr. "Chaos is the score upon which reality is written." --Henry Miller ___ python-committers mailing list python-committers@python.org http://mail.python.org/mailman/listinfo/python-committers
Re: [python-committers] Xs
On Mon, Jun 28, 2010 at 1:31 PM, Jesse Noller wrote: > Apparently my three year old knows how to work the mail app on my iPhone. Dang! Already tainted by closed-source technologies... -Fred -- Fred L. Drake, Jr. "A storm broke loose in my mind." --Albert Einstein ___ python-committers mailing list python-committers@python.org http://mail.python.org/mailman/listinfo/python-committers
Re: [python-committers] Eric Araujo (merwok) as Distutils commiter
On Tue, Aug 3, 2010 at 10:33 AM, Tarek Ziadé wrote: > So if everyone agrees Eric gets commit access, and works with me on > Distutils, and I stay the official maintainer +1 -Fred -- Fred L. Drake, Jr. "A storm broke loose in my mind." --Albert Einstein ___ python-committers mailing list python-committers@python.org http://mail.python.org/mailman/listinfo/python-committers
Re: [python-committers] Eric Araujo (merwok) as Distutils commiter
On Tue, Aug 3, 2010 at 11:23 AM, Antoine Pitrou wrote: > Let me point out something fishy: “Fred Drake” is almost an anagram of > “Tarek Ziadé”. Shhh! Nobody's supposed to know that "F" is spelled "qZ" on my birth certificate! -Fred -- Fred L. Drake, Jr. "A storm broke loose in my mind." --Albert Einstein ___ python-committers mailing list python-committers@python.org http://mail.python.org/mailman/listinfo/python-committers
Re: [python-committers] Commit privileges for Łukasz Langa
On Sun, Sep 5, 2010 at 10:43 AM, Antoine Pitrou wrote: > I propose we give commit privileges to Łukasz Langa. He has submitted > various non-trivial patches of rather good quality (for example new > features for ConfigParser), some of which have already been committed; +1 -Fred -- Fred L. Drake, Jr. "A storm broke loose in my mind." --Albert Einstein ___ python-committers mailing list python-committers@python.org http://mail.python.org/mailman/listinfo/python-committers
Re: [python-committers] Providing .tgz sources
On Sun, Dec 5, 2010 at 12:02 PM, Fredrik Lundh wrote: > (btw, someone mentioned bandwidth -- are we paying for bandwidth? what > fraction of the python.org traffic is downloads?) Even if the PSF isn't paying for bandwidth (and I don't know either way), users on the other end often are. This is understandable and real concern. If providing this new format helps them, I'd be all for that. -Fred -- Fred L. Drake, Jr. "A storm broke loose in my mind." --Albert Einstein ___ python-committers mailing list python-committers@python.org http://mail.python.org/mailman/listinfo/python-committers
Re: [python-committers] do we still believe explicit relative imports are bad as PEP 8 claims?
On Fri, Feb 18, 2011 at 3:36 PM, Brett Cannon wrote: > It says they are "highly discouraged" because "absolute imports are > more portable and usually more readable", but now that people have had > a chance to use explicit relative imports, do people still believe > this? I mean if we truly believed this then why did we add the syntax? > I know I have used it and love it, let alone that I don't buy the > portability argument. I suspect the portability argument is about cross-Python-version compatibility, rather than across operating systems. Maybe we don't care about that any more since 2.4 and earlier don't exist in the eyes of python-dev. On the other hand, I've never used them, or stumbled over code that does, so I won't speak to the readability issue. I have an opinion, but no practical experience with explicit relative imports. -Fred -- Fred L. Drake, Jr. "A storm broke loose in my mind." --Albert Einstein ___ python-committers mailing list python-committers@python.org http://mail.python.org/mailman/listinfo/python-committers
Re: [python-committers] do we still believe explicit relative imports are bad as PEP 8 claims?
On Fri, Feb 18, 2011 at 3:59 PM, Antoine Pitrou wrote: > (especially non-trivial variants such as "from ..foo import bar"). Eeewe. More than one leading "." should be considered a bug. -Fred -- Fred L. Drake, Jr. "A storm broke loose in my mind." --Albert Einstein ___ python-committers mailing list python-committers@python.org http://mail.python.org/mailman/listinfo/python-committers
Re: [python-committers] Recording committer status in the bug tracker
On Tue, Mar 15, 2011 at 11:22 PM, "Martin v. Löwis" wrote: > added a boolean flag to the bug tracker indicating what user accounts belong > to committers. I'm showing as a committer, but not that my contributor form has been received. I've pointed out the later problem before (some time ago), and there was no response. I know I've provided one. If someone could check on that, I'd appreciate it. If I need to submit a new form, I can do that as well. -Fred -- Fred L. Drake, Jr. "A storm broke loose in my mind." --Albert Einstein ___ python-committers mailing list python-committers@python.org http://mail.python.org/mailman/listinfo/python-committers
Re: [python-committers] Reminder: Python 3.4 alpha 1 release is Saturday August 3
On Fri, Aug 2, 2013 at 4:25 PM, Larry Hastings wrote: > From PEP 101, "Doing Python Releases 101": > > IT IS HIGHLY RECOMMENDED THAT YOU AT LEAST TAG THE TREE 24 HOURS > BEFORE A FINAL RELEASE. This will give the Experts enough time to > do their bits before the announcement goes out. > > The schedule calls for the Alpha 1 release tomorrow. Ergo, tag today. When I read this, I expect it to only apply to X.Y.Z releases, not alphas and betas. Which doesn't mean there should be an interval between the tagging and the release. (I expect a period this size for the first beta is just as valuable, since that's the API freeze.) For anything else, I think it's up to the release manager. > Should I add "expected tag dates" to the schedule? That, or some text explaining what to expect, would be good to have. -Fred -- Fred L. Drake, Jr. "A storm broke loose in my mind." --Albert Einstein ___ python-committers mailing list python-committers@python.org http://mail.python.org/mailman/listinfo/python-committers
Re: [python-committers] Please add your GitHub username to your bugs.python.org account
On Mon, May 2, 2016 at 4:15 PM, Antoine Pitrou wrote: > Perhaps GitHub refuses to send e-mail to the PythonLabs? Interesting hypothesis, but... my invite came by email just fine, and there wasn't any problem once accepted. Perhaps the PSU is involv ___ python-committers mailing list python-committers@python.org https://mail.python.org/mailman/listinfo/python-committers Code of Conduct: https://www.python.org/psf/codeofconduct/
