On Mon, 03 Sep 2012 22:37:31 +0200
"Martin v. Löwis" wrote:
> Am 03.09.2012 12:11, schrieb Antoine Pitrou:
> > Despite being undocumented, these two macros are used in a couple of
> > third-party extension modules (*) such as greenlet and py-judy. This
> > means that such an extension compiled for
On Mon, Sep 3, 2012 at 10:18 PM, anatoly techtonik wrote:
> On Sun, Sep 2, 2012 at 11:26 PM, Lennart Regebro wrote:
>> Switched from python-dev to python-porting.
>>
>> On Sun, Sep 2, 2012 at 9:48 PM, anatoly techtonik
>> wrote:
>>> I work offline from remote location about 2000m above the sea
Am 03.09.2012 12:11, schrieb Antoine Pitrou:
> Despite being undocumented, these two macros are used in a couple of
> third-party extension modules (*) such as greenlet and py-judy. This
> means that such an extension compiled for 2.7.3 wouldn't work with
> 2.7.4, and vice-versa. Is there something
On Sun, Sep 2, 2012 at 11:26 PM, Lennart Regebro wrote:
> Switched from python-dev to python-porting.
>
> On Sun, Sep 2, 2012 at 9:48 PM, anatoly techtonik wrote:
>> I work offline from remote location about 2000m above the sea level. There
>> is no internet connection here, so I can not use trac
Am 03.09.2012 16:27, schrieb Antoine Pitrou:
> You could ask infrastruct...@python.org for an account on an existing
> machine (dinsdale perhaps, it looks much less loaded now that some
> services have been migrated).
Thanks Antoine! I've contacted the infrastructure team.
Christian
__
On Mon, 03 Sep 2012 15:59:59 +0200
Christian Heimes wrote:
>
> It's easy, doesn't take much effort and can easily be automated, but
> somebody has to do it. The process should also be placed on the Python
> infrastructure and I don't have access. Secondly somebody has to contact
> Coverity to app
Hello everybody,
two weeks ago Stefan Krah asked for a current Coverity scan report.
Coverity has updated us to a new version with a new workflow. Before the
update Coverity pulled the code from our version control system. However
the latest version doesn't work that way. The code must be compiled
Hello,
To fix the crash in http://bugs.python.org/issue13992, I have to change
the definition of the Py_TRASHCAN_SAFE_BEGIN and Py_TRASHCAN_SAFE_END
macros in a way that makes them stop rely on global variables.
Despite being undocumented, these two macros are used in a couple of
third-party ext
