James Addison

> Perhaps: > > 1. Substitute the year iff it is the current year. > > 2. Add some format specifier (`{yy}` or `{yyyy}` or `%y` or `%Y` or `YY`...

> I'm back to business here Jay (really sorry for just contributing to CPython and forgetting about Sphinx). I like this plan because: No problem! Thank you for taking your...

Closing this as the detection-of-constants approach seems complex, and also since we are gaining agreement that we can use a simplified template string format instead.

@chrisjsewell it's been a while since we discussed this one, and I haven't seen many (any?) more reports about duplicate intersphinx entries, but even so it does still seem valid...

There's some time cost to reading more of the background/history here, but I think it could be valuable. While addressing a question on a separate thread, I've attempted to summarize...

I'm on the fence about whether to close this or not. I do think it's good to avoid creation/hosting of ambiguous references in the first place.. and/or to at least...

> I'm on the fence about whether to close this or not. I do think it's good to avoid creation/hosting of ambiguous references in the first place.. and/or to at...

Thank you @tokuhirom - the suggested changes look good to me. Is it possible to add a test to the `tests/js` directory to confirm that a client query behaves as...

An accessibility suggestion, because although I generally like these changes a lot, they do make the result list appear less like a standard HTML list visually: perhaps we should follow...

Maybe nitpicky: the horizontal margin/padding between the icons and the search result titles has increased; is there a way to reduce that back to near the original spacing?