[Python-Dev] editing the docs
Hi, Now that I'm starting to examine and do some edits on the docs, I'd like to ask some guidance. What editor(s) do you guys use? I'm not one to cling to an editor, so all suggestions are fair game. -- Thanks, Benjamin Peterson ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] editing the docs
Benjamin Peterson schrieb: > Hi, > Now that I'm starting to examine and do some edits on the docs, I'd like > to ask some guidance. What editor(s) do you guys use? I'm not one to > cling to an editor, so all suggestions are fair game. I use Emacs, for which the docutils bring an excellent rst mode. Georg -- Thus spake the Lord: Thou shalt indent with four spaces. No more, no less. Four shall be the number of spaces thou shalt indent, and the number of thy indenting shall be four. Eight shalt thou not indent, nor either indent thou two, excepting that thou then proceed to four. Tabs are right out. ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] editing the docs
> Now that I'm starting to examine and do some edits on the docs, I'd like > to ask some guidance. What editor(s) do you guys use? I'm not one to > cling to an editor, so all suggestions are fair game. For the docs, I typically use Emacs as well. Regards, Martin ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] editing the docs
-On [20080329 17:13], Benjamin Peterson ([EMAIL PROTECTED]) wrote: >Now that I'm starting to examine and do some edits on the docs, I'd like to ask >some guidance. What editor(s) do you guys use? I'm not one to cling to an >editor, so all suggestions are fair game. I personally use vim. But this question is really dependent on what you think works best. Some prefer command line tools, others graphical tools. Just try a few and see what you personally find to work nicely enough. -- Jeroen Ruigrok van der Werven / asmodai イェルーン ラウフロック ヴァン デル ウェルヴェン http://www.in-nomine.org/ | http://www.rangaku.org/ To love someone deeply gives you strength. Being loved by someone deeply gives you courage... ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] FreeBSD test suite failure -> curses
> Actually, given my recent results and discussion with Thomas Dickey I am not > so sure. Even if there is a bug in the test or in Python that causes newscr to become NULL - why does that not show up in other releases, or on other systems? > Thomas mentioned after seeing an ltrace: > > Perhaps it's failing on that: > > curses.setupterm(fd=sys.__stdout__.fileno()) > > That would have newscr null. The failure might be from closing stdout, e.g., > if it was redirected. Can you debug this and confirm that this call indeed sets newscr to NULL? At the point the test is run, stdout is not closed; instead, it is a pipe going to the build slave. Usually, all curses output shows up in the buildbot log (which doesn't really automatically test whether the right thing is happening - but we don't want to test the system's curses library, anyway). Regards, Martin ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] editing the docs
On Sat, Mar 29, 2008 at 12:25 PM, Jeroen Ruigrok van der Werven < [EMAIL PROTECTED]> wrote: > -On [20080329 17:13], Benjamin Peterson ([EMAIL PROTECTED]) > wrote: > >Now that I'm starting to examine and do some edits on the docs, I'd like > to ask > >some guidance. What editor(s) do you guys use? I'm not one to cling to an > >editor, so all suggestions are fair game. > > I personally use vim. But this question is really dependent on what you > think works best. Some prefer command line tools, others graphical tools. > Just try a few and see what you personally find to work nicely enough. Well, I do use emacs for my coding, so I'm going to try that mode out now. > > > -- > Jeroen Ruigrok van der Werven / asmodai > イェルーン ラウフロック ヴァン デル ウェルヴェン > http://www.in-nomine.org/ | http://www.rangaku.org/ > To love someone deeply gives you strength. Being loved by someone deeply > gives you courage... > -- Cheers, Benjamin Peterson ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] FreeBSD test suite failure -> curses
-On [20080329 18:37], "Martin v. Löwis" ([EMAIL PROTECTED]) wrote:
>Even if there is a bug in the test or in Python that causes newscr to
>become NULL - why does that not show up in other releases, or on other
>systems?
I have been breaking my head about that as well. But then again it is just
as strange that from a script run it does not coredump whereas running from
the interactive prompt or from the testsuite it does. That should, in
principle, not be much different either.
>Can you debug this and confirm that this call indeed sets newscr to NULL?
Breakpoint 1, 0x283119f8 in setupterm () from /lib/libncursesw.so.6
(gdb) print newscr
$1 = 0
(gdb) cont
Continuing.
Breakpoint 1, 0x283119f8 in setupterm () from /lib/libncursesw.so.6
(gdb) print newscr
$2 = 0
(gdb) cont
Continuing.
Hardware access (read/write) watchpoint 2:
{} 674382472
Value = 0
0x2836e102 in PyCurses_getsyx (self=0x0)
at /usr/home/asmodai/projects/python/Modules/_cursesmodule.c:1770
1770 getsyx(y, x);
(gdb) print newscr
$3 = (WINDOW *) 0x0
If you have any specific debug guidance, please feel free to give so. :)
--
Jeroen Ruigrok van der Werven / asmodai
イェルーン ラウフロック ヴァン デル ウェルヴェン
http://www.in-nomine.org/ | http://www.rangaku.org/
The superior person uses his mind like a mirror: it accepts all, it
reflects all. It receives, but it does not keep...
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] nested classes leaking in compiler
Georg Brandl schrieb: > Somehow I knew you'd be the one to find the problem :) Agreed! :) Amaury is really good in finding loose ends in the parser and AST code. I still can't wrap my brain around the AST code but it can see the light at the end of the code. ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] nested classes leaking in compiler
Christian Heimes wrote:
> Georg Brandl schrieb:
>
> > Somehow I knew you'd be the one to find the problem :)
>
> Agreed! :)
>
> Amaury is really good in finding loose ends in the parser and AST code.
> I still can't wrap my brain around the AST code but it can see the light
> at the end of the code.
Actually the ast compiler is the part I know least in CPython code.
The approach I used is a bit brute-force, but it may work for other
reference leaks:
- First write a big leaking script:
for x in xrange(10): leaking_function()
- Since memory usage does not increase dramatically, it's only a
refcount problem - no new object every time.
- Modify the Py_INCREF macro so that it generates a breakpoint in the
debugger when the refcount is large:
On Windows, it is something like:
if (ob->refcount > 1) { __asm int 3; }
(with gdb I think you may signal SIGUSR1)
- carefully inspect the code each time the debugger stops.
Fortunately, many functions can be skipped: PyDict_SetItem and other
bullet-proof parts of the code.
The 20th break was the good one: a lack of symmetry between
Py_INCREF and Py_DECREF.
--
Amaury Forgeot d'Arc
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Python source code on Bazaar vcs
On Thu, Mar 20, 2008 at 2:42 PM, Barry Warsaw <[EMAIL PROTECTED]> wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > I'm happy to announce that we now have available for public > consumption, the Python source code for 2.5, 2.6 and 3.0 available > under the Bazaar distributed version control system. > > The current Subversion repository is still the master copy of the > source code. We have not made a decision to move to Bazaar > officially, nor have we made a decision to even move off of > Subversion. We're making these branches available exactly so that > you, the Python developer community, can kick the tires and see if it > makes sense to move to a different vcs. Nothing will happen until > after the Python 2.6/3.0 releases anyway. > > All the gory details are documented here: > > http://www.python.org/dev/bazaar > > These branches are available both for core Python developers with > commit privileges, and the wider world of developers without commit > privileges. It's this latter group that I think will find the most > compelling immediate benefit from using Bazaar, because they will no > longer need to maintain their own changes using a mass of patch files. > > For more information on Bazaar in general, see: > > http://bazaar-vcs.org > > You will probably be most interested in the Bazaar mirrors of the > Subversion master repository. We have a cron job that updates Bazaar > from Subversion every 15 minutes. It is also possible to push changes > made in your Bazaar branches into the Subversion master, so you can > keep reasonably up-to-date and interact with the Python source code > solely via Bazaar. Once you've pushed the branches, is there a way to remove them? > > > Please let me know if you have any questions or anything in the docs > referenced above aren't clear. I know I need to document the Bazaar- > >Subversion workflow in more detail. > > Huge thanks go out especially to Thomas Wouters who sprinted with me > yesterday on getting the whole infrastructure up and running. Thanks > also to Martin v. Loewis, Sean Reifschneider, and the folks here at > Pycon from the Bazaar project, Ian, Andrew, John, and Edwin. > > Enjoy, > - -Barry > > -BEGIN PGP SIGNATURE- > Version: GnuPG v1.4.8 (Darwin) > > iQCVAwUBR+K+H3EjvBPtnXfVAQL6bwP/d0XKx0mRPgzdOD6zCPwwRl8y2kxWV9Vl > zVwN07cK8IlwMa9M470MsERuXuD8hmeXnPgnrUcrX9HciwldmY8C33t0f8GaOk1J > iD4Od1midlIaJJiMd+JcFk9NbX3Rwc4HMj3s8jKjjdlGrFe77ei9DCZ/HMl/iG5K > fyyjXo4HLEE= > =Gcjq > -END PGP SIGNATURE- > ___ > Python-Dev mailing list > Python-Dev@python.org > http://mail.python.org/mailman/listinfo/python-dev > Unsubscribe: > http://mail.python.org/mailman/options/python-dev/musiccomposition%40gmail.com > -- Cheers, Benjamin Peterson ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Python source code on Bazaar vcs
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Mar 29, 2008, at 5:11 PM, Benjamin Peterson wrote: > Once you've pushed the branches, is there a way to remove them? Do you mean the local branches? If yes, then 'rm -rf mymergedbranch' does exactly what you want. :) - -Barry -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.8 (Darwin) iQCVAwUBR+67qXEjvBPtnXfVAQJ94AP8CA6OmnIlOluIfUuW1TolCpZQJTZS3TbL 4ZZS32CYvgF4gB366wAuaFGuCsaQlAV9punP5l0T9Ei6i4cHD1nIKheNY49JfLxX 83I5fXV9n+Mwe0uJEjgfP5GKTykawwTypG6zfy2lkvJm4wwhfHUH26ctafOlVXo1 z4bLDFZsMMs= =KQay -END PGP SIGNATURE- ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Python source code on Bazaar vcs
On Sat, Mar 29, 2008 at 4:59 PM, Barry Warsaw <[EMAIL PROTECTED]> wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On Mar 29, 2008, at 5:11 PM, Benjamin Peterson wrote: > > > Once you've pushed the branches, is there a way to remove them? > > Do you mean the local branches? If yes, then 'rm -rf mymergedbranch' > does exactly what you want. :) No, I mean the pushed version on code.python.org. > > > - -Barry > > -BEGIN PGP SIGNATURE- > Version: GnuPG v1.4.8 (Darwin) > > iQCVAwUBR+67qXEjvBPtnXfVAQJ94AP8CA6OmnIlOluIfUuW1TolCpZQJTZS3TbL > 4ZZS32CYvgF4gB366wAuaFGuCsaQlAV9punP5l0T9Ei6i4cHD1nIKheNY49JfLxX > 83I5fXV9n+Mwe0uJEjgfP5GKTykawwTypG6zfy2lkvJm4wwhfHUH26ctafOlVXo1 > z4bLDFZsMMs= > =KQay > -END PGP SIGNATURE- > -- Cheers, Benjamin Peterson ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Python source code on Bazaar vcs
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Mar 29, 2008, at 6:00 PM, Benjamin Peterson wrote: > > No, I mean the pushed version on code.python.org. Not unless you have shell or sftp access, which you probably don't. It's not a big deal though except for a mild feeling of uncleanliness. If you ever want to push a completely unrelated branch overtop that one, just use --overwrite. - -Barry -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.8 (Darwin) iQCVAwUBR+6+ZnEjvBPtnXfVAQIbdgP+KRv3Uhq9OQrhc6iRI1eEVR+1bbYbFSQs bwvwSf9SXNaf/YfO5Bm61YlJkHHkJd0237cf0Dn/MU8IFacRawJijhVbBYec2QmY 4CWeMiiPop+LL1z2MlXkErfbeVt9AZeiNQ/oDLYda9Bg7Tw20XKE3VYqJGAVGt0b XrucWkxI964= =ahtL -END PGP SIGNATURE- ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Python source code on Bazaar vcs
Benjamin> Once you've pushed the branches, is there a way to remove them? Related question: is there a way to view the various branches in a non-local repository? Skip ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
