On Wed, Sep 01, 2010 at 06:41:00AM +0300, Eli Bendersky wrote:
I would like to ask those of you working on
Python's code with VIM about your setups - the special tweaks to VIM
plugins you use to make working with the code as simple and effective as
possible.
You have already seen Misc/Vim
On Wed, Sep 1, 2010 at 8:42 AM, Antoine Pitrou solip...@pitrou.net wrote:
After all, we don't usually try to workaround platform-specific
bugs (not as a low level such as the C API level); at worse, we mention
their existence in the docs.
You persist in viewing the allowance of multiple C
Le mercredi 01 septembre 2010 à 22:43 +1000, Nick Coghlan a écrit :
On Wed, Sep 1, 2010 at 8:42 AM, Antoine Pitrou solip...@pitrou.net wrote:
After all, we don't usually try to workaround platform-specific
bugs (not as a low level such as the C API level); at worse, we mention
their
On 01/09/2010 13:54, Antoine Pitrou wrote:
[snip...]
Please consider this: even without relying on PEP 384, using FILE*
is /already/ dangerous; because you might compile an extension with a
different compiler version than Python was compiled with. So, if we were
following you, we should rip out
On 24/08/2010 08:40, Michael Foord wrote:
On 24/08/2010 01:25, Nick Coghlan wrote:
On Tue, Aug 24, 2010 at 8:15 AM, Nick Coghlanncogh...@gmail.com wrote:
Now, it may be worth considering an addition to the inspect module
that was basically:
def getattr_static(obj, attr):
Retrieve attributes
On 25 August 2010 20:57, P.J. Eby p...@telecommunity.com wrote:
[snip...]
As you can see, the __call__ attribute in each case is whatever the proxied
object's __call__ attribute is, even though the proxy itself has a __call__
method, that is invoked when the proxy is called.
This is
On Wed, Sep 1, 2010 at 10:54 PM, Antoine Pitrou solip...@pitrou.net wrote:
Please consider this: even without relying on PEP 384, using FILE*
is /already/ dangerous; because you might compile an extension with a
different compiler version than Python was compiled with. So, if we were
following
On Thu, 2 Sep 2010 07:04:31 +1000
Nick Coghlan ncogh...@gmail.com wrote:
On Wed, Sep 1, 2010 at 10:54 PM, Antoine Pitrou solip...@pitrou.net wrote:
Please consider this: even without relying on PEP 384, using FILE*
is /already/ dangerous; because you might compile an extension with a
That title isn't better though, since it doesn't cover the using/cmdline
document which deals with command line options, environment variables
and the like.
I agree that Using Python is not very descriptive though.
Georg
Am 01.09.2010 10:57, schrieb raymond.hettinger:
Author: raymond.hettinger
On Thu, Sep 2, 2010 at 7:19 AM, Antoine Pitrou solip...@pitrou.net wrote:
Maybe I've missed your answer, but what would prevent the inline
solution from working?
Only PEP 7 (since standard support for inline is a C99 feature)
On the other hand, if gcc (including cygwin/mingw) and MSVC support
On Wed, Sep 1, 2010 at 10:58 PM, antoine.pitrou
python-check...@python.org wrote:
Modified: python/branches/py3k/Misc/NEWS
==
--- python/branches/py3k/Misc/NEWS (original)
+++ python/branches/py3k/Misc/NEWS
On Thu, Sep 2, 2010 at 7:25 AM, Georg Brandl g.bra...@gmx.net wrote:
That title isn't better though, since it doesn't cover the using/cmdline
document which deals with command line options, environment variables
and the like.
I agree that Using Python is not very descriptive though.
Python
12 matches
Mail list logo
