Home Original page

[Python-Dev] Any Emacs tips for core developers?

Barry Warsaw barry at python.org
Tue Feb 5 03:22:05 CET 2008 
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Feb 4, 2008, at 7:47 PM, skip at pobox.com wrote:

>
>>> I should have asked this before, but what's so special about core
>>> (Python?)  development that the tools should be different than for
>>> non-core development?
>
>    Brett> Usually the core has keywords, built-ins, etc. that have  
> not been
>    Brett> pushed to the release versions for various editors.
>
> Ah, okay.  Barry mentioned something about adjusting the python-mode  
> syntax
> tables to include Python 3.x stuff, though patches are always
> welcome. <wink>

If left to me, it might not happen until I start writing a lot of  
Python 3 code :).

>    Brett> Plus coding guidelines might be different from PEPs 7 and 8
>    Brett> compared to what an editor is set to do by default.
>
> That might be a bit more challenging.  I was thinking today that it  
> would be
> kind of nice to have a set of predefined settings for Python's new C  
> style
> (someone mentioned producing that).  Should that go in the C/C++  
> mode or be
> delivered somehow else?

I think it might not be horrible if python-mode.el included a function  
that installed Python's new C style, which you could then select  
through your mode hook or whatever.  It's been ages since I hacked on  
that stuff, but I wonder how far Python's new C style differs from the  
built-in styles.  Maybe there's one that's already close enough?

- -Barry

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (Darwin)

iQCVAwUBR6fITXEjvBPtnXfVAQIlZwQApRs/VC2tV7auSRjK2AuWuFf7i/k5EPTf
ZaBSgmHtb8jENTvOZju2XOnOVdhlgHO5Zec5ptvXKc3Y1Mzl9API2RjH0jP9G8mt
mzI22bGScnCbA5bpzM7kh5cyg939+GzUmUF7BsRoAquIwKRdf5NHbJG+qcxKO0pK
vcKIuf6eJxM=
=Ltuj
-----END PGP SIGNATURE-----
More information about the Python-Dev mailing list