New submission from Nick Coghlan ncogh...@gmail.com:
From
http://posted-stuff.blogspot.com/2011/01/bug-reporting-energy-depleted.html
The author of that blog post tried to search for capi to see if a particular
crash had already been reported. The default search and a search in all fields
New submission from Nick Coghlan ncogh...@gmail.com:
Pretty simple - it would be good to have a Devguide component in the tracker,
separate from the normal Documentation component.
Useful for things like: http://bugs.python.org/issue11690
--
messages: 1933
nosy: brett.cannon, ncoghlan
New submission from Nick Coghlan ncogh...@gmail.com:
The diff generator seems to get confused when the most recent merge with
default was via a different branch: http://bugs.python.org/issue11682
The pep380 branch in my BitBucket sandbox depends on the new feature in the
get_opinfo branch, so
New submission from Nick Coghlan ncogh...@gmail.com:
Every time I hit Create Patch on issue 11816 for my get_opinfo branch, I get
the error message: 9512712044a6.diff is already available
It first started happening when I hit 'Create Patch' after unlinking the
previous diff (which used
Nick Coghlan ncogh...@gmail.com added the comment:
Yeah, something simple like your first suggestion should work reasonably well.
Since the dependencies and superceder nouns are ambiguous about the
direction of the relationship, and aren't particularly common words anyway,
it's probably
Nick Coghlan ncogh...@gmail.com added the comment:
I'm not a big fan either, but it's the simplest option available that displays
the relevant information. Here's a more complex option that may work:
1. Keep the existing Dependencies/Superceder fields for editing purposes
(perhaps changing
Nick Coghlan added the comment:
This hit me as well (because rerunning a query with the same name in the saved
field creates a new copy rather than overwriting the original). Potentially
related is the fact that in addition to delete not working, the dropdowns don't
let me change the query
New submission from Nick Coghlan:
setuptools maintenance has moved to the Python Packaging Authority account on
BitBucket for version 0.7 and later:
https://bitbucket.org/pypa/setuptools/issues?status=newstatus=open
While the tracker on bug.python.org needs to remain open for 0.6 updates
Nick Coghlan added the comment:
I'm not sure why the direct link isn't working, but if you click on the
"46.4.197.70" heading it will take you through to the detailed report.
"High"lights:
* This server supports weak Diffie-Hellman (DH) key exchange parameters
Nick Coghlan added the comment:
Guido: good points, so I've instead filed
https://github.com/python/devguide/issues/38 to discuss updating the Triaging
section of the devguide with a bit more guidance on when it's a good idea to
set these keywords
Nick Coghlan added the comment:
OK, I've created the "easy (C)" keyword: http://bugs.python.org/keyword18
I've left the existing "easy" keyword alone for the time being, as the Python
vs Documentation split is already implied by the component, but changing the
keyword to &
Nick Coghlan added the comment:
If we're tinkering with the "easy" tag, would it make sense to switch to a more
objectively definable phrase like "well defined (Python)" and "well defined
(C)"?
The reason I ask is that good starter issues for folks that
Nick Coghlan added the comment:
Awesome, thank you all!
___
PSF Meta Tracker <metatrac...@psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta
Nick Coghlan added the comment:
Adding a note about http://psf.upfronthosting.co.za/roundup/meta/issue636: the
"patch" keyword currently isn't being set for issues that *only* have a linked
PR, which is throwing off both the "Open issues with patches" metrics, an
New submission from Nick Coghlan:
I'm unclear on exactly when this server is going to be moving to a different
PSF-controlled domain, and
https://wiki.python.org/moin/TrackerDevelopment#The_Meta_Tracker doesn't
provide any info either.
--
messages: 3364
nosy: mmangoba, ncoghlan
Nick Coghlan added the comment:
I've added Mark Mangoba (the PSF's Infrastructure Manager) to the nosy list, as
the meta-tracker should also be moved to a PSF controlled domain now that
bugs.python.org itself has been moved to be directly under PSF management
rather than being managed
Nick Coghlan added the comment:
As per https://github.com/python/bugs.python.org/issues/1 (and #655 as Eric
linked above), I'm now proposing that we switch the meta-tracker over to
GitHub, since we don't need the workflow customisation for bugs.python.org
itself that we currently want
Nick Coghlan added the comment:
Marking as obsolete given CPython's migration to GitHub (part of the
https://github.com/python/bugs.python.org/issues/1 issue review)
--
nosy: +ncoghlan
status: chatting -> resolved
___
PSF M
New submission from Nick Coghlan :
Hi folks,
bugs.python.org is currently a key piece of CPython workflow automation, but
it's relatively difficult to contribute to as it uses a different workflow from
both CPython itself *and* the rest of the core workflow projects (cherry
picker, blurb
Nick Coghlan added the comment:
Issue-tracker-only repos technically aren't sourceless, but the trick is that
the only file you create is a README, and perhaps some issue templates:
https://github.com/python/bugs.python.org
Alternatively, they can also be good places to host the source code
Nick Coghlan added the comment:
I've migrated this issue over to the new meta-tracker at
https://github.com/python/bugs.python.org/issues/10
This is one of several problems with the existing bugs.python.org
infrastructure that are leading to it being rehosted elsewhere, and I've tagged
Nick Coghlan added the comment:
Note that a potential variation of the new approach is that rather than
reseeding the default instance, the Action could create and seed a new
random.Random() instance every time. It would be slightly slower, but I don't
think this gets hit often enough
Nick Coghlan added the comment:
Huh, I'd never noticed how easy that documentation is to miss: it's in the
preamble text at the start of https://docs.python.org/3/library/random.html
I filed https://bugs.python.org/issue33783 to suggest giving it some proper
Sphinx markup
New submission from Nick Coghlan <ncogh...@gmail.com>:
When accessing the bug tracker, Firefox intermittently reports
SEC_ERROR_BAD_SIGNATURE. While a refresh usually fixes the problem, this
suggests to me that something isn't quite right with the current host
configuration.
(P
24 matches
Mail list logo
