Skip to content

Instantly share code, notes, and snippets.

Brett Cannon brettcannon

Block or report user

Report or block brettcannon

Hide content and notifications from this user.

Learn more about blocking users

Contact Support about this user’s behavior.

Learn more about reporting abuse

Report abuse
View GitHub Profile
@brettcannon
brettcannon / parse_wheel_filename.py
Created May 8, 2019
Parse a wheel filename using packaging.tags
View parse_wheel_filename.py
import packaging.tags
def parse_wheel_filename(path):
name = os.path.splitext(_compat.fspath(path))[0]
index = len(name)
for _ in range(3): # interpreter, ABI, platform.
index = name.rindex("-", 0, index)
return packaging.tags.parse_tag(name[index + 1 :])
@brettcannon
brettcannon / cloudSettings
Last active Jun 18, 2018
Visual Studio Code Settings Sync Gist
View cloudSettings
{"lastUpload":"2018-06-18T21:57:18.905Z","extensionVersion":"v2.9.2"}
@brettcannon
brettcannon / parse-pylint-list-msgs.py
Last active Mar 9, 2018
Parse the Pylint message list
View parse-pylint-list-msgs.py
import pathlib
import re
SUMMARY_LINE_RE = re.compile(r':(?P<name>\S+) \((?P<code>.+?)\):( \*(?P<summary>.+)\*)?')
def parse_summary_line(line):
line_match = SUMMARY_LINE_RE.match(line)
if not line_match:
raise ValueError(f"ill-formed line: {line!r}")
@brettcannon
brettcannon / hglookup.py
Last active Nov 28, 2017
hg.python.org/lookup
View hglookup.py
# hglookup.py
#
# Lookup a revision hash in a bunch of different hgwebdir repos.
# Also includes special treatment for subversion revisions from
# the CPython repo.
#
# Written by Georg Brandl, 2010.
import io
import json
@brettcannon
brettcannon / 3.5-comparison.txt
Created Sep 13, 2016
Performance comparison between Python 3.5.2+ & 3.6b1+
View 3.5-comparison.txt
+------------------------------------+---------------+---------------+--------------+-------------------------+
| Benchmark | 3.5-perf.json | 3.6-perf.json | Change | Significance |
+====================================+===============+===============+==============+=========================+
| 2to3 | 0.68 | 0.62 | 1.09x faster | Significant (t=65.03) |
+------------------------------------+---------------+---------------+--------------+-------------------------+
| call_method | 0.02 | 0.02 | 1.07x faster | Significant (t=46.01) |
+------------------------------------+---------------+---------------+--------------+-------------------------+
| call_method_slots | 0.02 | 0.02 | 1.06x faster | Significant (t=29.45) |
+------------------------------------+---------------+---------------+--------------+-------------------------+
| call_method_un
@brettcannon
brettcannon / fspath.py
Created Apr 13, 2016
Possibly implementations of os.fspath()
View fspath.py
# str-only.
def fspath(path):
try:
path = path.__fspath__()
except AttributeError:
pass
if isinstance(path, str):
return path
else:
raise TypeError
View An unscientific survey of Python interpreters.ipynb
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
View Porting Python 2 code to Python 3.ipynb
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
@brettcannon
brettcannon / gist:a9c9a5989dc383ed73b4
Last active Sep 19, 2017
Initial email about Python development process and proposed improvements
View gist:a9c9a5989dc383ed73b4

This was posted as an email to python-dev.

History lesson

Since I signed up for the python-dev mailing list way back in June 2002, there seems to be a cycle where we as a group come to a realization that our current software development process has not kept up with modern practices and could stand for an update. For me this was first shown when we moved from SourceForge to our own infrastructure, then again when we moved from Subversion to Mercurial (I led both of these initiatives, so it's somewhat a tradition/curse I find myself in this position yet again). And so we again find ourselves at the point of realizing that we are not keeping up with current practices and thus need to evaluate how we can improve our situation.

Where we are now

Now it should be realized that we have to sets of users of our development process: contributors and core developers (the latter whom can play both roles). If you take a rough outline of our cur

View keybase.md

Keybase proof

I hereby claim:

  • I am brettcannon on github.
  • I am brettcannon (https://keybase.io/brettcannon) on keybase.
  • I have a public key whose fingerprint is D78A 1843 8650 EA2D FE58 817F 9668 94F3 4B4E ABA8

To claim this, I am signing this object:

You can’t perform that action at this time.