On Wed, Jan 6, 2010 at 7:32 PM, Benjamin Peterson wrote:
> 2010/1/6 John Arbash Meinel :
> > 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 increfing and setting the exception state,
2010/1/6 John Arbash Meinel :
> 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 than back at 5).
Correct.
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
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 c
On Wed, Jan 6, 2010 at 19:28, Brett Cannon wrote:
>
>
> On Wed, Jan 6, 2010 at 17:22, R. David Murray wrote:
>
>>
>> On Wed, 06 Jan 2010 11:03:32 -0800, Brett Cannon wrote:
>> > On Wed, Jan 6, 2010 at 06:57, Brian Curtin
>> wrote:
>> > > On the topic of bugs that can be readily closed (literally
On Wed, Jan 6, 2010 at 17:22, R. David Murray wrote:
>
> On Wed, 06 Jan 2010 11:03:32 -0800, Brett Cannon wrote:
> > On Wed, Jan 6, 2010 at 06:57, Brian Curtin
> wrote:
> > > On the topic of bugs that can be readily closed (literally), I've
> recently
> > > come across a number of issues which a
On Wed, 06 Jan 2010 11:03:32 -0800, Brett Cannon wrote:
> On Wed, Jan 6, 2010 at 06:57, Brian Curtin 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, but their patche
On Wed, Jan 6, 2010 at 17:21, "Martin v. Löwis" 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 pointer, tha
> 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
Pyth
On Wed, Jan 6, 2010 at 16:14, Nicholas Bastin 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 /u1/tmp/python2.7a1, but the
(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
In article <4b4475f3.5040...@gmail.com>,
Nick Coghlan 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 info
On Wed, Jan 6, 2010 at 06:57, Brian Curtin wrote:
> On Wed, Jan 6, 2010 at 06:57, Nick Coghlan 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.
Antoine Pitrou 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 bee
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
> "Nick" == Nick Coghlan 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:
http://mail.python.org/mailman/listinfo
On Jan 6, 2010, at 7:29 AM, Tarek Ziadé wrote:
> On Wed, Jan 6, 2010 at 12:24 PM, Michael Foord
> 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
On Wed, Jan 6, 2010 at 06:57, Nick Coghlan 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 pass, just sayin
On Wed, 06 Jan 2010 11:41:28 +, Chris Withers
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 completeness, ther
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
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 informati
On Wed, Jan 6, 2010 at 1:31 PM, Chris Withers 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 days at PyCo
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 12:24 PM, Michael Foord
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 is the knowled
On Wed, Jan 6, 2010 at 8:19 AM, Chris Withers 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
> notifications of new bugs...
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
- http://w
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 no
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 ow
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 d
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 notifica
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
--
Simplistix
31 matches
Mail list logo
