RetroSearch Browse

Mon Mar 27 18:30:22 CEST 2006 · https://mail.python.org/pipermail/python-dev/2006-March/062866.html

>> Why don't we expose _PySet_Next() for Barry and leave it out of the  public 
>> API
>> for everyone else.

[Alex]
> There are precedents for adding some functionality to the C API but  not 
> documenting it to ensure "non advanced users" don't get hurt --  that's how we 
> added the ability to raise exceptions in different  threads, in particular. 
> Not sure if this is the best solution here,  but I'm just pointing out that 
> it's definitely not "unthinkable",  procedurally speaking.

Thank would be nice.  It gives me the ability to keep a clean, sane API while at 
the same time making sure that my most important customer (Barry) gets his needs 
met.

Raymond 

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2006-March/062866.html below:

[Python-Dev] PySet API