Hi All,
Is there a high volume of incoming bugs to the Python tracker?
If so, I'd like to help with triaging. I think I have all the necessary
access, what I'm missing is the knowledge of how to set myself up to get
notifications of new bugs...
How do I do that?
cheers,
Chris
--
Hi Chris,
Is there a high volume of incoming bugs to the Python tracker?
If so, I'd like to help with triaging. I think I have all the necessary
access, what I'm missing is the knowledge of how to set myself up to get
notifications of new bugs...
Do you really want to get such
On 06/01/2010 11:19, Chris Withers wrote:
Hi All,
Is there a high volume of incoming bugs to the Python tracker?
If so, I'd like to help with triaging. I think I have all the
necessary access, what I'm missing is the knowledge of how to set
myself up to get notifications of new bugs...
How
Michael Foord wrote:
I assumed there would be RSS feeds for bug tracker activity but can't
easily find these on the tracker. There is a bot that posts activity to
#python-dev, so there must be some way of getting this information.
Yeah, email-out is what I'm really after... I have it for my
Michael Foord wrote:
I assumed there would be RSS feeds for bug tracker activity but can't
easily find these on the tracker. There is a bot that posts activity to
#python-dev, so there must be some way of getting this information.
I'm pretty sure the bugs list is still the primary spooled
Nick Coghlan wrote:
I'm pretty sure the bugs list is still the primary spooled notification
mechanism:
http://mail.python.org/mailman/listinfo/python-bugs-list
That's what I was after, thanks!
Chris
--
Simplistix - Content Management, Batch Processing Python Consulting
-
On Wed, Jan 6, 2010 at 8:19 AM, Chris Withers ch...@simplistix.co.uk wrote:
Is there a high volume of incoming bugs to the Python tracker?
If so, I'd like to help with triaging. I think I have all the necessary
access, what I'm missing is the knowledge of how to set myself up to get
On Wed, Jan 6, 2010 at 12:24 PM, Michael Foord
fuzzy...@voidspace.org.uk wrote:
On 06/01/2010 11:19, Chris Withers wrote:
Hi All,
Is there a high volume of incoming bugs to the Python tracker?
If so, I'd like to help with triaging. I think I have all the necessary
access, what I'm missing
Tarek Ziadé wrote:
Another useful triage I think, is to review the oldest bugs (some of
them are 5 years)
and remove the ones that are not relevant anymore, or duplicate with
newer entries.
I'm sprinting for 2 days at PyCon, I'd verymuch be up for doing this
with someone as a paired task for
On Wed, Jan 6, 2010 at 1:31 PM, Chris Withers ch...@simplistix.co.uk wrote:
Tarek Ziadé wrote:
Another useful triage I think, is to review the oldest bugs (some of
them are 5 years)
and remove the ones that are not relevant anymore, or duplicate with
newer entries.
I'm sprinting for 2
On Wed, 2010-01-06 at 11:30 +, Chris Withers wrote:
Michael Foord wrote:
I assumed there would be RSS feeds for bug tracker activity but can't
easily find these on the tracker. There is a bot that posts activity to
#python-dev, so there must be some way of getting this information.
Tarek Ziadé wrote:
Another useful triage I think, is to review the oldest bugs (some of
them are 5 years)
and remove the ones that are not relevant anymore, or duplicate with
newer entries.
I believe someone (Daniel Diniz, maybe?) did do a pass over those some
time in the last 12 months, so
On Wed, 06 Jan 2010 11:41:28 +, Chris Withers ch...@simplistix.co.uk
wrote:
Nick Coghlan wrote:
I'm pretty sure the bugs list is still the primary spooled notification
mechanism:
http://mail.python.org/mailman/listinfo/python-bugs-list
That's what I was after, thanks!
Just for
On Wed, Jan 6, 2010 at 06:57, Nick Coghlan ncogh...@gmail.com wrote:
I believe someone (Daniel Diniz, maybe?) did do a pass over those some
time in the last 12 months, so most of the obviously irrelevant ones
that are that old should already be gone. Not to say it isn't worth
doing another
On Jan 6, 2010, at 7:29 AM, Tarek Ziadé wrote:
On Wed, Jan 6, 2010 at 12:24 PM, Michael Foord
fuzzy...@voidspace.org.uk wrote:
On 06/01/2010 11:19, Chris Withers wrote:
Hi All,
Is there a high volume of incoming bugs to the Python tracker?
If so, I'd like to help with triaging. I think
Nick == Nick Coghlan ncogh...@gmail.com writes:
Nick I'm pretty sure the bugs list is still the primary spooled
Nick notification mechanism:
Nick http://mail.python.org/mailman/listinfo/python-bugs-list
Actually, there is a new-bugs-announce list:
Le Wed, 06 Jan 2010 08:57:42 -0600, Brian Curtin a écrit :
On the topic of bugs that can be readily closed (literally), I've
recently come across a number of issues which appear to be sitting in a
patch or review stage, but their patches have been committed and the
issue remains open. What is
Antoine Pitrou solipsis at pitrou.net writes:
Le Wed, 06 Jan 2010 08:57:42 -0600, Brian Curtin a écrit :
On the topic of bugs that can be readily closed (literally), I've
recently come across a number of issues which appear to be sitting in a
patch or review stage, but their patches have
On Wed, Jan 6, 2010 at 06:57, Brian Curtin brian.cur...@gmail.com wrote:
On Wed, Jan 6, 2010 at 06:57, Nick Coghlan ncogh...@gmail.com wrote:
I believe someone (Daniel Diniz, maybe?) did do a pass over those some
time in the last 12 months, so most of the obviously irrelevant ones
that are
In article 4b4475f3.5040...@gmail.com,
Nick Coghlan ncogh...@gmail.com wrote:
Michael Foord wrote:
I assumed there would be RSS feeds for bug tracker activity but can't
easily find these on the tracker. There is a bot that posts activity to
#python-dev, so there must be some way of getting
(This may occur on more platforms - I can test on more unix platforms
if the consensus is this is an actual problem and I'm not just a nut)
On freebsd5, if you do a simple ./configure --enable-shared in current
(2.7) trunk, your python shared library will build properly, but all
modules will fail
On Wed, Jan 6, 2010 at 16:14, Nicholas Bastin nick.bas...@gmail.com wrote:
This of course is because libpython2.7.so is in the current directory
and not (yet) installed in /usr/local/lib.
One minor correction - as you could see from the compile line, the
actual --prefix in this case is
b) Does this fix seem like the sensible thing to do?
No. Linking in setup.py should use the same options as if the module
was built as *shared* through Modules/Setup, which, IIUC, should use
BLDLIBRARY.
Regards,
Martin
___
Python-Dev mailing list
On Wed, Jan 6, 2010 at 17:21, Martin v. Löwis mar...@v.loewis.de wrote:
b) Does this fix seem like the sensible thing to do?
No. Linking in setup.py should use the same options as if the module
was built as *shared* through Modules/Setup, which, IIUC, should use
BLDLIBRARY.
Thanks for that
On Wed, 06 Jan 2010 11:03:32 -0800, Brett Cannon wrote:
On Wed, Jan 6, 2010 at 06:57, Brian Curtin brian.cur...@gmail.com wrote:
On the topic of bugs that can be readily closed (literally), I've recently
come across a number of issues which appear to be sitting in a patch or
review stage,
On Wed, Jan 6, 2010 at 17:22, R. David Murray rdmur...@bitdance.com wrote:
On Wed, 06 Jan 2010 11:03:32 -0800, Brett Cannon wrote:
On Wed, Jan 6, 2010 at 06:57, Brian Curtin brian.cur...@gmail.com
wrote:
On the topic of bugs that can be readily closed (literally), I've
recently
come
On Wed, Jan 6, 2010 at 19:28, Brett Cannon br...@python.org wrote:
On Wed, Jan 6, 2010 at 17:22, R. David Murray rdmur...@bitdance.comwrote:
On Wed, 06 Jan 2010 11:03:32 -0800, Brett Cannon wrote:
On Wed, Jan 6, 2010 at 06:57, Brian Curtin brian.cur...@gmail.com
wrote:
On the topic of
Hi,
I've been wondering whether it's possible to release the GIL in the
regex engine during matching.
I know that it needs to have the GIL during memory-management calls, but
does it for calls like Py_UNICODE_TOLOWER or PyErr_SetString? Is there
an easy way to find out? Or is it just a case of
MRAB wrote:
Hi,
I've been wondering whether it's possible to release the GIL in the
regex engine during matching.
I know that it needs to have the GIL during memory-management calls, but
does it for calls like Py_UNICODE_TOLOWER or PyErr_SetString? Is there
an easy way to find out? Or is
2010/1/6 John Arbash Meinel john.arbash.mei...@gmail.com:
Anything that Py_INCREF or Py_DECREF's should have the GIL, or you may
get concurrent updating of the value, and then the final value is wrong.
(two threads do 5+1 getting 6, rather than 7, and when the decref, you
end up at 4 rather
On Wed, Jan 6, 2010 at 7:32 PM, Benjamin Peterson benja...@python.org wrote:
2010/1/6 John Arbash Meinel john.arbash.mei...@gmail.com:
AFAIK, the only things that don't require the GIL are macro functions,
like PyString_AS_STRING or PyTuple_SET_ITEM. PyErr_SetString, for
example, will be
31 matches
Mail list logo
