From barry at python.org Wed Jan 5 19:45:08 2011 From: barry at python.org (Barry Warsaw) Date: Wed, 5 Jan 2011 13:45:08 -0500 Subject: [Python-mode] Time for a new release? Message-ID: <20110105134508.28c700b3@python.org> Thanks Andreas and Georg for your recent commits to python-mode.el. I wonder if it isn't time to start thinking about an official release, probably of 5.2? Is there anything else anybody would like to get in, say over the next couple of days? If not, I'd be happy to do a release on Friday, but wouldn't mind if someone else wanted to do it instead. -Barry -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 836 bytes Desc: not available URL: From andreas.roehler at online.de Wed Jan 5 20:45:52 2011 From: andreas.roehler at online.de (=?ISO-8859-1?Q?Andreas_R=F6hler?=) Date: Wed, 05 Jan 2011 20:45:52 +0100 Subject: [Python-mode] Time for a new release? In-Reply-To: <20110105134508.28c700b3@python.org> References: <20110105134508.28c700b3@python.org> Message-ID: <4D24CA70.3030003@online.de> Am 05.01.2011 19:45, schrieb Barry Warsaw: > Thanks Andreas and Georg for your recent commits to python-mode.el. I wonder > if it isn't time to start thinking about an official release, probably of 5.2? > Is there anything else anybody would like to get in, say over the next couple > of days? If not, I'd be happy to do a release on Friday, but wouldn't mind if > someone else wanted to do it instead. > > -Barry > > > > _______________________________________________ > Python-mode mailing list > Python-mode at python.org > http://mail.python.org/mailman/listinfo/python-mode Hi Barry, I'm glad seeing python-mode proceeding. As for a release, AFAIU we don't have reached Milestone 5.1.1 yet. Bug #473525 isn't dealt with. Wanted to look at next days. Too for my taste there are much more bugs we could adress an current code base still. I'm pretty sure more triple-quote-string bugs exists. Hopefully I'll be at it next month. Cheers Andreas From skip at pobox.com Wed Jan 5 20:41:48 2011 From: skip at pobox.com (skip at pobox.com) Date: Wed, 5 Jan 2011 13:41:48 -0600 Subject: [Python-mode] Time for a new release? In-Reply-To: <4D24CA70.3030003@online.de> References: <20110105134508.28c700b3@python.org> <4D24CA70.3030003@online.de> Message-ID: <19748.51580.648429.827369@montanaro.dyndns.org> >> Thanks Andreas and Georg for your recent commits to python-mode.el. Ditto. >> I wonder if it isn't time to start thinking about an official >> release, probably of 5.2? Is there anything else anybody would like >> to get in, say over the next couple of days? If not, I'd be happy to >> do a release on Friday, but wouldn't mind if someone else wanted to >> do it instead. Any chance of making something available without announcing globally? I really don't have the round tuits necessary to figure out the launchpad stuff. I could, however, download and install from a tarball and test it a bit. Skip From barry at python.org Wed Jan 5 22:08:05 2011 From: barry at python.org (Barry Warsaw) Date: Wed, 5 Jan 2011 16:08:05 -0500 Subject: [Python-mode] Time for a new release? In-Reply-To: <19748.51580.648429.827369@montanaro.dyndns.org> References: <20110105134508.28c700b3@python.org> <4D24CA70.3030003@online.de> <19748.51580.648429.827369@montanaro.dyndns.org> Message-ID: <20110105160805.125d5a5e@python.org> On Jan 05, 2011, at 01:41 PM, skip at pobox.com wrote: >Any chance of making something available without announcing globally? I >really don't have the round tuits necessary to figure out the launchpad >stuff. I could, however, download and install from a tarball and test it a >bit. In Launchpad we can only attach download files to releases, and I don't think it makes sense to put dev versions on stable releases. We could find another way to do it, but actually the easiest way to always get the current bzr head is: % bzr --no-plugins cat http://bazaar.launchpad.net/~python-mode-devs/python-mode/python-mode/python-mode.el > python-mode.el (yeah the repetition sucks, but oh well, it works) -Barry -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 836 bytes Desc: not available URL: From barry at python.org Wed Jan 5 22:13:06 2011 From: barry at python.org (Barry Warsaw) Date: Wed, 5 Jan 2011 16:13:06 -0500 Subject: [Python-mode] Time for a new release? In-Reply-To: <4D24CA70.3030003@online.de> References: <20110105134508.28c700b3@python.org> <4D24CA70.3030003@online.de> Message-ID: <20110105161306.5a1fb66b@python.org> On Jan 05, 2011, at 08:45 PM, Andreas R?hler wrote: >I'm glad seeing python-mode proceeding. > >As for a release, AFAIU we don't have reached Milestone 5.1.1 yet. Please consider whether the changes so far warrant a 5.1.1 or a 5.2. I haven't looked closely enough, but I'd say if there are new features, then 5.2 is probably more appropriate. We can always retarget issues to a new milestone. (Next time, we can also not care until we actually do a release.) >Bug #473525 isn't dealt with. >Wanted to look at next days. Georg just committed a fix for this, which works for me. >Too for my taste there are much more bugs we could adress an current code >base still. > >I'm pretty sure more triple-quote-string bugs exists. >Hopefully I'll be at it next month. Cool. You're doing most of the work, so you should decide! There are always more version numbers where the last one came from though. :) -Barry -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 836 bytes Desc: not available URL: From georg at python.org Wed Jan 5 22:19:46 2011 From: georg at python.org (Georg Brandl) Date: Wed, 05 Jan 2011 22:19:46 +0100 Subject: [Python-mode] Time for a new release? In-Reply-To: <20110105161306.5a1fb66b@python.org> References: <20110105134508.28c700b3@python.org> <4D24CA70.3030003@online.de> <20110105161306.5a1fb66b@python.org> Message-ID: <4D24E072.4060508@python.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Am 05.01.2011 22:13, schrieb Barry Warsaw: > On Jan 05, 2011, at 08:45 PM, Andreas R?hler wrote: > >>I'm glad seeing python-mode proceeding. >> >>As for a release, AFAIU we don't have reached Milestone 5.1.1 yet. > > Please consider whether the changes so far warrant a 5.1.1 or a 5.2. I > haven't looked closely enough, but I'd say if there are new features, then 5.2 > is probably more appropriate. We can always retarget issues to a new > milestone. > > (Next time, we can also not care until we actually do a release.) > >>Bug #473525 isn't dealt with. >>Wanted to look at next days. > > Georg just committed a fix for this, which works for me. Ah yes, sorry for not updating or referencing the report. >>Too for my taste there are much more bugs we could adress an current code >>base still. >> >>I'm pretty sure more triple-quote-string bugs exists. >>Hopefully I'll be at it next month. > > Cool. You're doing most of the work, so you should decide! There are always > more version numbers where the last one came from though. :) +1. Georg -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) iEYEARECAAYFAk0k4HIACgkQN9GcIYhpnLBttgCdESwU9UY8FM6XI7TLDP+guL2p NagAoJ3n1goBoGw7tNGl1rx5m149vi3q =Au8w -----END PGP SIGNATURE----- From georg at python.org Wed Jan 5 21:58:23 2011 From: georg at python.org (Georg Brandl) Date: Wed, 05 Jan 2011 21:58:23 +0100 Subject: [Python-mode] Time for a new release? In-Reply-To: <20110105134508.28c700b3@python.org> References: <20110105134508.28c700b3@python.org> Message-ID: <4D24DB6F.30603@python.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Am 05.01.2011 19:45, schrieb Barry Warsaw: > Thanks Andreas and Georg for your recent commits to python-mode.el. I wonder > if it isn't time to start thinking about an official release, probably of 5.2? > Is there anything else anybody would like to get in, say over the next couple > of days? If not, I'd be happy to do a release on Friday, but wouldn't mind if > someone else wanted to do it instead. I have some more changes that I'd like to discuss before committing. (These are features in my patched version at bitbucket.org/birkenfeld/dotemacs). Basically: * a separate face for class names: font-lock-type-face is meant for types in type declarations and therefore usually not a very noticeable face. For example I like to have class names underlined, but having font-lock-type-face underlined looks very odd in c-mode. * a separate face for exception classes: somewhat redundant, but looks nice. Both for builtin exceptions and any name after a raise or except. * special locking for escape sequences and %-formatting codes in strings, like the equivalent feature in elisp-mode. (The code seems to have some issues with font-locking buffers, so I'd be glad for suggestions how to fix it.) * no filling in code (that one is pretty simple, just remove the "fill- paragraph" in the last condition of py-fill-paragraph). BTW, while looking at this, something is still not quite right with the parsing of triple-quoted string literals... as can be witnessed when filling a TQS with embedded SQS... If I can figure out how to do it, I'll commit these changes separately to a private branch on launchpad, so that they can be reviewed. Georg -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) iEYEARECAAYFAk0k228ACgkQN9GcIYhpnLDI1gCgmu12TOxOMNI7Yy+C81kbvqjs 8UoAnA7eos3Tpm1YcRt5s7AJxPiN36iD =kDPB -----END PGP SIGNATURE----- From barry at python.org Thu Jan 6 00:19:57 2011 From: barry at python.org (Barry Warsaw) Date: Wed, 5 Jan 2011 18:19:57 -0500 Subject: [Python-mode] Time for a new release? In-Reply-To: <4D24DB6F.30603@python.org> References: <20110105134508.28c700b3@python.org> <4D24DB6F.30603@python.org> Message-ID: <20110105181957.7de85653@python.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi Georg, On Jan 05, 2011, at 09:58 PM, Georg Brandl wrote: >I have some more changes that I'd like to discuss before committing. (These >are features in my patched version at bitbucket.org/birkenfeld/dotemacs). > >Basically: > >* a separate face for class names: font-lock-type-face is meant for types in > type declarations and therefore usually not a very noticeable face. For > example I like to have class names underlined, but having > font-lock-type-face underlined looks very odd in c-mode. > >* a separate face for exception classes: somewhat redundant, but looks nice. > Both for builtin exceptions and any name after a raise or except. Both of these sound good to me. I checked out and tested your branch, and reviewed it. I think there are only two minor issues that need fixing, but it otherwise looks good. >* special locking for escape sequences and %-formatting codes in strings, like > the equivalent feature in elisp-mode. > > (The code seems to have some issues with font-locking buffers, so I'd be > glad for suggestions how to fix it.) I'm not sure I understand what the issues are. I tested it with a few Mailman files and it looked okay, though the extra bolding was a little off-putting (yeah, I'll be customizing those faces as soon as your changes land :). What are the problems? Not that I'm an expert on all the insane font-lock possibilities. >* no filling in code (that one is pretty simple, just remove the "fill- > paragraph" in the last condition of py-fill-paragraph). +1! If that's the bug I think it is, it's been annoying me for about a bazillion years. E.g. I want to be able to fill comments for sure, maybe strings, but never code. >BTW, while looking at this, something is still not quite right with the >parsing of triple-quoted string literals... as can be witnessed when filling >a TQS with embedded SQS... Can you provide an example? >If I can figure out how to do it, I'll commit these changes separately to a >private branch on launchpad, so that they can be reviewed. Two additional things would be nice if anyone's so inclined. * Adding a NEWS file; I don't care how far back into history it goes. * Maybe some nice screen grabs of face examples so folks have a visual way of seeing what their font-lock options are. - -Barry -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iQIcBAEBCAAGBQJNJPydAAoJEBJutWOnSwa/eLMP/AmfQCJEpEHLRuKr2lyoTeFL rlZFwF8k1ypn3J0UASqlt5xMgUJGwZLZklyedoRtzFe5Q7ubqWn7rFlTITEcP9UP PmJhIZOhpt5TtwRC+wCKaKOFx2YtycbPn5rL0CRW0AZh5rsZTqFa35Gzl08Iqzuo 7qNoTDqt6hNaN8AdNS1XxGvGv4ydHjX21JM2lFAGYhuBcUpSXdZ4D19nNh/X460Y IIdiQQRWgcmiqwefiQQcTxDndYQadAVvhSDwOrukdcSnfOxp6nKTXS5SWp55BbUo Gzzx38C9emnESMKjChvfkSlTkjw58SUEwuBdRKCdX0oluGUf13xGaVaFmQRx0Fu3 +oqCMa0tXx0b29E2HzP00V7TcCQeWCCwqW03qN10xBWIxdfYFlVIpA4zh+MG5nUe h+8AVzGO9MTCImsIC6UQLSi318oq0dOGp0Mr05Y0HYv4v6sv+TUhWZIqMVZvsqLJ D5ob0y85bvrLCWva1HI09K7AOWLw1cHIRNZwGRJ++SubrDGdwd3diZYQUcWhGTpP CHLTRM7eSBjCMvASzHMD7upePFI9Hkn5zJTybCLtMsMC8FXpyNJbbmY9Elnx2x98 Z4VPL/dhS/42rXGU7tBfHdCMbtm7RNq2uKK7noKP0SY3UHZ83YFqBUkZiUsHvHdU JnPOgzCQAHqj7CFzwPvy =OKPX -----END PGP SIGNATURE----- From max at alcyone.com Thu Jan 6 06:02:57 2011 From: max at alcyone.com (Erik Max Francis) Date: Wed, 05 Jan 2011 21:02:57 -0800 Subject: [Python-mode] Time for a new release? In-Reply-To: <20110105181957.7de85653@python.org> References: <20110105134508.28c700b3@python.org> <4D24DB6F.30603@python.org> <20110105181957.7de85653@python.org> Message-ID: <4D254D01.102@alcyone.com> Barry Warsaw wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA256 > > Hi Georg, > > On Jan 05, 2011, at 09:58 PM, Georg Brandl wrote: >> BTW, while looking at this, something is still not quite right with the >> parsing of triple-quoted string literals... as can be witnessed when filling >> a TQS with embedded SQS... > > Can you provide an example? Embed a single-quoted string in a triple-quoted one: """This is a "single-quoted string" inside a triple-quoted one.""" It does not color properly; the contents inside the single-quoted string are not colored as if it were part of the string. -- Erik Max Francis && max at alcyone.com && http://www.alcyone.com/max/ San Jose, CA, USA && 37 18 N 121 57 W && AIM/Y!M/Skype erikmaxfrancis Many situations can be clarified by the passing of time. -- Theodore Isaac Rubin From georg at python.org Thu Jan 6 09:00:59 2011 From: georg at python.org (Georg Brandl) Date: Thu, 06 Jan 2011 09:00:59 +0100 Subject: [Python-mode] Time for a new release? In-Reply-To: <20110105181957.7de85653@python.org> References: <20110105134508.28c700b3@python.org> <4D24DB6F.30603@python.org> <20110105181957.7de85653@python.org> Message-ID: <4D2576BB.10102@python.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Am 06.01.2011 00:19, schrieb Barry Warsaw: > Hi Georg, > > On Jan 05, 2011, at 09:58 PM, Georg Brandl wrote: > >>I have some more changes that I'd like to discuss before committing. (These >>are features in my patched version at bitbucket.org/birkenfeld/dotemacs). > >>Basically: > >>* a separate face for class names: font-lock-type-face is meant for types in >> type declarations and therefore usually not a very noticeable face. For >> example I like to have class names underlined, but having >> font-lock-type-face underlined looks very odd in c-mode. > >>* a separate face for exception classes: somewhat redundant, but looks nice. >> Both for builtin exceptions and any name after a raise or except. > > Both of these sound good to me. I checked out and tested your branch, and > reviewed it. I think there are only two minor issues that need fixing, but it > otherwise looks good. Okay, I'll have a look at the customization issue. >>* special locking for escape sequences and %-formatting codes in strings, like >> the equivalent feature in elisp-mode. > >> (The code seems to have some issues with font-locking buffers, so I'd be >> glad for suggestions how to fix it.) > > I'm not sure I understand what the issues are. I tested it with a few Mailman > files and it looked okay, though the extra bolding was a little off-putting > (yeah, I'll be customizing those faces as soon as your changes land :). > > What are the problems? Not that I'm an expert on all the insane font-lock > possibilities. The problem is that after applying this patch, I see larger files mis-highlighted when I open them and jump to somewhere in the middle of the buffer (or when the point is placed there automatically on openening, because that was my last editing position). Basically, I guess some string boundary isn't recognized, and the highlighting string <-> code is reversed: code is highlighted as string, and vice versa. It can be "fixed" by moving point into a correctly highlighted region and calling `font-lock-fontify-buffer'. >>* no filling in code (that one is pretty simple, just remove the "fill- >> paragraph" in the last condition of py-fill-paragraph). > > +1! If that's the bug I think it is, it's been annoying me for about a > bazillion years. E.g. I want to be able to fill comments for sure, maybe > strings, but never code. Yep, that's that. >>BTW, while looking at this, something is still not quite right with the >>parsing of triple-quoted string literals... as can be witnessed when filling >>a TQS with embedded SQS... > > Can you provide an example? Try filling this string: """ The output conforms to the XHTML version 1.0 Transitional DTD (*almost* strict). The output "contains" a minimum of formatting information. The cascading style sheet "html4css1.css" is required for proper viewing with a modern graphical browser. """ It results in this: """ The output conforms to the XHTML version 1.0 Transitional DTD (*almost* strict). The output"contains" a minimum of formatting information. The cascading style sheet "html4css1.css" is required for proper viewing with a modern graphical browser. """ behaving as if the string stopped at the single double-quote before "contains". The font-locking *seems* to be all-right, however I've still seen an instance where the text between the single quotes has code-coloring -- cannot reproduce though. >>If I can figure out how to do it, I'll commit these changes separately to a >>private branch on launchpad, so that they can be reviewed. > > Two additional things would be nice if anyone's so inclined. > > * Adding a NEWS file; I don't care how far back into history it goes. > * Maybe some nice screen grabs of face examples so folks have a visual way of > seeing what their font-lock options are. I'll see what I can do. cheers, Georg -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) iEYEARECAAYFAk0ldrsACgkQN9GcIYhpnLA0RQCdHtQEmfop4YFg0zv8r6H0uA5I oYEAn21pHlLZllzlnKanPwh76DyGQea3 =HFI+ -----END PGP SIGNATURE----- From barry at python.org Thu Jan 6 17:55:58 2011 From: barry at python.org (Barry Warsaw) Date: Thu, 6 Jan 2011 11:55:58 -0500 Subject: [Python-mode] Time for a new release? In-Reply-To: <4D254D01.102@alcyone.com> References: <20110105134508.28c700b3@python.org> <4D24DB6F.30603@python.org> <20110105181957.7de85653@python.org> <4D254D01.102@alcyone.com> Message-ID: <20110106115558.069c42c3@python.org> On Jan 05, 2011, at 09:02 PM, Erik Max Francis wrote: >Embed a single-quoted string in a triple-quoted one: > >"""This is a "single-quoted string" inside a triple-quoted one.""" > >It does not color properly; the contents inside the single-quoted string are >not colored as if it were part of the string. wfm with r372 in Emacs 23.2.1 -Barry -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 836 bytes Desc: not available URL: From barry at python.org Thu Jan 6 18:01:30 2011 From: barry at python.org (Barry Warsaw) Date: Thu, 6 Jan 2011 12:01:30 -0500 Subject: [Python-mode] Time for a new release? In-Reply-To: <4D2576BB.10102@python.org> References: <20110105134508.28c700b3@python.org> <4D24DB6F.30603@python.org> <20110105181957.7de85653@python.org> <4D2576BB.10102@python.org> Message-ID: <20110106120130.44ef9c8f@python.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On Jan 06, 2011, at 09:00 AM, Georg Brandl wrote: >Okay, I'll have a look at the customization issue. It doesn't appear to affect behavior and I have no idea how to fix it, so I think it shouldn't block your branch. >The problem is that after applying this patch, I see larger files >mis-highlighted when I open them and jump to somewhere in the middle of the >buffer (or when the point is placed there automatically on openening, because >that was my last editing position). > >Basically, I guess some string boundary isn't recognized, and the highlighting >string <-> code is reversed: code is highlighted as string, and vice versa. >It can be "fixed" by moving point into a correctly highlighted region and >calling `font-lock-fontify-buffer'. But with no change to the buffer other than that? Sounds like possibly a bug in Emacs, though I also vaguely recall that font-lock did or does have some maximum limit of buffer size on which it operated. I think this was put in at the time where then-modern machines really couldn't keep up with on-the-fly highlighting. >>>BTW, while looking at this, something is still not quite right with the >>>parsing of triple-quoted string literals... as can be witnessed when filling >>>a TQS with embedded SQS... >> >> Can you provide an example? > >Try filling this string: > >""" >The output conforms to the XHTML version 1.0 Transitional DTD >(*almost* strict). The output "contains" a minimum of formatting >information. The cascading style sheet "html4css1.css" is required >for proper viewing with a modern graphical browser. >""" > >It results in this: > >""" >The output conforms to the XHTML version 1.0 Transitional DTD (*almost* strict). >The output"contains" a minimum of formatting >information. The cascading style sheet "html4css1.css" is required >for proper viewing with a modern graphical browser. >""" > >behaving as if the string stopped at the single double-quote before >"contains". Confirmed, and if you change those embedded double quotes to single quotes, the paragraph fills correctly. >The font-locking *seems* to be all-right, however I've still seen an instance >where the text between the single quotes has code-coloring -- cannot reproduce >though. Me neither with r372. >>>If I can figure out how to do it, I'll commit these changes separately to a >>>private branch on launchpad, so that they can be reviewed. >> >> Two additional things would be nice if anyone's so inclined. >> >> * Adding a NEWS file; I don't care how far back into history it goes. >> * Maybe some nice screen grabs of face examples so folks have a visual way of >> seeing what their font-lock options are. > >I'll see what I can do. Thanks very much for adding the NEWS file! - -Barry -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iQIcBAEBCAAGBQJNJfVrAAoJEBJutWOnSwa/rdEP/i+yMLtXrdvDLDDLJQj8lb2i ra0m5vPsRJ3lx++Y+vEQuiDSK47tg0LZOBprG9L4V+UbO/prQj9VvDYSxxQxKiF4 xbZXSPjzBeEc6SEXKlXceWt/GQTF/8D3481CwAihqsthfC+6qgrUSnfowzW/wJXj eNZUMHOOvBfHBwpWCYXGT0ZO0qMoJ4lbau+GOz/BBNnKYKO0K7+mDrywM6rheibz DLvSbYnUhFlwxQsNDkPDG33K5ZMb9+IOLj9bjBxYzEAP74eD2to1u7rGDKh7Nh+s gT5R30d81LjfYNlAbYx2X7cUwRxPdHeYMGFQtVyTZofgno+P1jYb+ML5QtR5Z2nI lIBFxSRcjEpOe7YOMld0srcRPt3NZkhF3IPU0TLtIic9gpf1fvjCFN/6nrQ1aczQ 10O23KB8gqIrJlX9V8oOnYeaM0n9VNpb/Bo+c4LPjHBe99N5/76HmwLCsa8/FwfT 4Gt06OfSxpLe5C7Ws7jpJH7eUG3ZRmsXy7/xcpPoXue8augVJCwHG+H8rHXYYQ2q cykYWbB6ZNQtKSEO8c7L/BiOx5nLXwbNJwPbTwJ88vtPo0DoIofM/FFNlGX7nVgk 4rXgCtox75NqS5fOzs01i4M9awaO4+Ml5pswhR9LaqXLCjA07exIpBdjsJwIgR3K 1AqOLi2PAnrtGoofO6VW =rdfN -----END PGP SIGNATURE----- From georg at python.org Fri Jan 7 12:24:16 2011 From: georg at python.org (Georg Brandl) Date: Fri, 07 Jan 2011 12:24:16 +0100 Subject: [Python-mode] Time for a new release? In-Reply-To: <20110106120130.44ef9c8f@python.org> References: <20110105134508.28c700b3@python.org> <4D24DB6F.30603@python.org> <20110105181957.7de85653@python.org> <4D2576BB.10102@python.org> <20110106120130.44ef9c8f@python.org> Message-ID: <4D26F7E0.2050203@python.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Am 06.01.2011 18:01, schrieb Barry Warsaw: > On Jan 06, 2011, at 09:00 AM, Georg Brandl wrote: > >>Okay, I'll have a look at the customization issue. > > It doesn't appear to affect behavior and I have no idea how to fix it, so I > think it shouldn't block your branch. OK, it is now merged. >>The problem is that after applying this patch, I see larger files >>mis-highlighted when I open them and jump to somewhere in the middle of the >>buffer (or when the point is placed there automatically on openening, because >>that was my last editing position). > >>Basically, I guess some string boundary isn't recognized, and the highlighting >>string <-> code is reversed: code is highlighted as string, and vice versa. >>It can be "fixed" by moving point into a correctly highlighted region and >>calling `font-lock-fontify-buffer'. > > But with no change to the buffer other than that? Sounds like possibly a bug > in Emacs, though I also vaguely recall that font-lock did or does have some > maximum limit of buffer size on which it operated. I think this was put in at > the time where then-modern machines really couldn't keep up with on-the-fly > highlighting. Meanwhile, I found the bug -- I was trying to do too much at once. But please do test the solution as well. cheers, Georg -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) iEYEARECAAYFAk0m9+AACgkQN9GcIYhpnLDTmQCffXCW3F0RA9zwNfzTNQ9fCjch 4tsAn0lQOVYJdSr9jWumRMYZKmPI1gnj =XzXn -----END PGP SIGNATURE----- From barry at python.org Fri Jan 7 16:49:36 2011 From: barry at python.org (Barry Warsaw) Date: Fri, 7 Jan 2011 10:49:36 -0500 Subject: [Python-mode] Time for a new release? In-Reply-To: <4D26F7E0.2050203@python.org> References: <20110105134508.28c700b3@python.org> <4D24DB6F.30603@python.org> <20110105181957.7de85653@python.org> <4D2576BB.10102@python.org> <20110106120130.44ef9c8f@python.org> <4D26F7E0.2050203@python.org> Message-ID: <20110107104936.0e371db8@python.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On Jan 07, 2011, at 12:24 PM, Georg Brandl wrote: >> It doesn't appear to affect behavior and I have no idea how to fix it, so I >> think it shouldn't block your branch. > >OK, it is now merged. Cool, thanks. >Meanwhile, I found the bug -- I was trying to do too much at once. But please >do test the solution as well. I've got r374 and will test it with real world code over the next few days. - -Barry -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iQIcBAEBCAAGBQJNJzYQAAoJEBJutWOnSwa/Q7QQAI4lnzTNbfKhYsp0uGDQcj7N qHtA0zR8oD32KAc6GauWpTJBF/Y4tGkssshLgZ0PVgsEdcUGXyWjNPCWVDeYFBTf pA4ZFSct/8+gGCIukCRtT9RjvuxCSTnbmWxH6ngiaezFv6xSGOtcJwjnecPxtPt2 nSoJ+b0FQA9YyBjFqbrnKKNHel8M0TKFbuv3VGa/P6qy+GobBLdA9/OOzvbP41rs ZrK0OIbBjQdZ+DV6of2CYs2fcq5ojLfa0QbNPqvUexPso4vNxGCrMAU3Y4Q+I9ze xkM9siPrbHinjSiQ+mR+3bzIcj3Nfhbe23R4ul3gpu1dMbeIj6z60bODUv0SJyr2 kK/bCSAmI+k6c+74ETcx5fgDONkyZ4Vz7iPbTsshp2XVUY+ehASgYbKuDkYzeZwM /nSc2/lFiP4Guly/fQdkBfXhnbzRqka72XJGOfLblUlsrnd8BWijY+1dKxhMIFQo hjVDiuTxSJZ0wHX8aGUZHKcLoRjhgjNy62N/lYDd62FPVQplEMxyqd2HrzXDvOfY eHqb0wozB0AAqJ3wGtgDmgFx3EvZKIF0QpBAUaYmG0FQcEE3OehfpF9mkXPThVfW 0+eKEYZzYPoHiRl0CHiWZsYj795NxEehgF3HiFWdiDyHJVJARfKc3vWKyavn+x6M V37/1oywiJPrxFEi0jjO =3EwK -----END PGP SIGNATURE----- From andreas.roehler at online.de Sat Jan 8 09:17:07 2011 From: andreas.roehler at online.de (=?ISO-8859-15?Q?Andreas_R=F6hler?=) Date: Sat, 08 Jan 2011 09:17:07 +0100 Subject: [Python-mode] milestone 5.1.1 Message-ID: <4D281D83.9020608@online.de> Hi Barry, looks like milestone is reached now. As Skip asked for a tarball... Cheers Andreas From barry at python.org Sat Jan 8 22:37:55 2011 From: barry at python.org (Barry Warsaw) Date: Sat, 8 Jan 2011 16:37:55 -0500 Subject: [Python-mode] milestone 5.1.1 In-Reply-To: <4D281D83.9020608@online.de> References: <4D281D83.9020608@online.de> Message-ID: <20110108163755.5f22a3e0@python.org> On Jan 08, 2011, at 09:17 AM, Andreas R?hler wrote: >looks like milestone is reached now. >As Skip asked for a tarball... Okay, it looks like r377 is it, right? If neither you or Georg plan to make any more commits, I'll tag this version and do the release. Let me know. -Barry -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 836 bytes Desc: not available URL: From georg at python.org Sat Jan 8 22:43:51 2011 From: georg at python.org (Georg Brandl) Date: Sat, 08 Jan 2011 22:43:51 +0100 Subject: [Python-mode] milestone 5.1.1 In-Reply-To: <20110108163755.5f22a3e0@python.org> References: <4D281D83.9020608@online.de> <20110108163755.5f22a3e0@python.org> Message-ID: <4D28DA97.7090702@python.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Am 08.01.2011 22:37, schrieb Barry Warsaw: > On Jan 08, 2011, at 09:17 AM, Andreas R?hler wrote: > >>looks like milestone is reached now. >>As Skip asked for a tarball... > > Okay, it looks like r377 is it, right? If neither you or Georg plan to make > any more commits, I'll tag this version and do the release. Let me know. I'm not sure whether to keep the string-escaping highlighting; I've started seeing mishighlighted files again... did anyone else notice something? Georg -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) iEYEARECAAYFAk0o2pcACgkQN9GcIYhpnLC/CwCfaa7CVQgmozwSUGVJguqjSzwD HmoAoIN+MJX8/O+OYr6bBWmniWzERYkf =LYR4 -----END PGP SIGNATURE----- From barry at python.org Sat Jan 8 22:57:14 2011 From: barry at python.org (Barry Warsaw) Date: Sat, 8 Jan 2011 16:57:14 -0500 Subject: [Python-mode] milestone 5.1.1 In-Reply-To: <4D28DA97.7090702@python.org> References: <4D281D83.9020608@online.de> <20110108163755.5f22a3e0@python.org> <4D28DA97.7090702@python.org> Message-ID: <20110108165714.72ed06b2@python.org> On Jan 08, 2011, at 10:43 PM, Georg Brandl wrote: >I'm not sure whether to keep the string-escaping highlighting; I've started >seeing mishighlighted files again... did anyone else notice something? I haven't yet, but I also haven't done a lot of Python hacking with the latest rev. I will over the next few days, so perhaps we should let r377 bake for a few days and either fix the problem, or do a release early next week. -Barry -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 836 bytes Desc: not available URL: From andreas.roehler at online.de Sat Jan 8 23:08:36 2011 From: andreas.roehler at online.de (=?ISO-8859-1?Q?Andreas_R=F6hler?=) Date: Sat, 08 Jan 2011 23:08:36 +0100 Subject: [Python-mode] milestone 5.1.1 In-Reply-To: <20110108165714.72ed06b2@python.org> References: <4D281D83.9020608@online.de> <20110108163755.5f22a3e0@python.org> <4D28DA97.7090702@python.org> <20110108165714.72ed06b2@python.org> Message-ID: <4D28E064.90202@online.de> Am 08.01.2011 22:57, schrieb Barry Warsaw: > On Jan 08, 2011, at 10:43 PM, Georg Brandl wrote: > >> I'm not sure whether to keep the string-escaping highlighting; I've started >> seeing mishighlighted files again... did anyone else notice something? > > I haven't yet, but I also haven't done a lot of Python hacking with the latest > rev. I will over the next few days, so perhaps we should let r377 bake for a > few days and either fix the problem, or do a release early next week. > > -Barry > > Wondered why the graph of milestone doesn't show its fullfilled. Seems, it requires a "released" declaration. Both tasks, where the milestone is declared for, are signaled "committed". So we get the tarball BTW Andreas From barry at python.org Sun Jan 9 02:27:06 2011 From: barry at python.org (Barry Warsaw) Date: Sat, 8 Jan 2011 20:27:06 -0500 Subject: [Python-mode] milestone 5.1.1 In-Reply-To: <4D28E064.90202@online.de> References: <4D281D83.9020608@online.de> <20110108163755.5f22a3e0@python.org> <4D28DA97.7090702@python.org> <20110108165714.72ed06b2@python.org> <4D28E064.90202@online.de> Message-ID: <20110108202706.5e144002@python.org> On Jan 08, 2011, at 11:08 PM, Andreas R?hler wrote: >Wondered why the graph of milestone doesn't show its fullfilled. >Seems, it requires a "released" declaration. There's no such state as 'fulfilled' afaik. Yes, we'll have to explicitly push the 'released' button. Note that it's also possible to operate without formal milestones. In that case, when you release, you essentially create the milestone for the release right then and there. >Both tasks, where the milestone is declared for, are signaled "committed". So >we get the tarball BTW Since Georg has one last outstanding issue, let's wait for him to give the green light and then I'll make the release. -Barry -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 836 bytes Desc: not available URL: From georg at python.org Sun Jan 9 08:29:21 2011 From: georg at python.org (Georg Brandl) Date: Sun, 09 Jan 2011 08:29:21 +0100 Subject: [Python-mode] milestone 5.1.1 In-Reply-To: <20110108202706.5e144002@python.org> References: <4D281D83.9020608@online.de> <20110108163755.5f22a3e0@python.org> <4D28DA97.7090702@python.org> <20110108165714.72ed06b2@python.org> <4D28E064.90202@online.de> <20110108202706.5e144002@python.org> Message-ID: <4D2963D1.4050301@python.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Am 09.01.2011 02:27, schrieb Barry Warsaw: > On Jan 08, 2011, at 11:08 PM, Andreas R?hler wrote: > >>Wondered why the graph of milestone doesn't show its fullfilled. >>Seems, it requires a "released" declaration. > > There's no such state as 'fulfilled' afaik. Yes, we'll have to explicitly > push the 'released' button. Note that it's also possible to operate without > formal milestones. In that case, when you release, you essentially create the > milestone for the release right then and there. > >>Both tasks, where the milestone is declared for, are signaled "committed". So >>we get the tarball BTW > > Since Georg has one last outstanding issue, let's wait for him to give the > green light and then I'll make the release. I've now commented out the problematic code -- I'll try to find out more and maybe ask the Emacs devs, but it's not important enough to hold up a relese. BTW, NEWS says "New in version 5.2.0", so if you want to call the release 5.1.1 you have to adapt this; however I'd say there are enough changes to warrant a minor-version step. cheers, Georg -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) iEYEARECAAYFAk0pY9EACgkQN9GcIYhpnLCznwCfbgaihN4ZKLmKxKLcmGG/yeOx 1NsAn1UAJMJkxThbhdGz7HPomEzFF3qw =/5VC -----END PGP SIGNATURE----- From barry at python.org Sun Jan 9 13:46:11 2011 From: barry at python.org (Barry Warsaw) Date: Sun, 9 Jan 2011 07:46:11 -0500 Subject: [Python-mode] milestone 5.1.1 In-Reply-To: <4D2963D1.4050301@python.org> References: <4D281D83.9020608@online.de> <20110108163755.5f22a3e0@python.org> <4D28DA97.7090702@python.org> <20110108165714.72ed06b2@python.org> <4D28E064.90202@online.de> <20110108202706.5e144002@python.org> <4D2963D1.4050301@python.org> Message-ID: <20110109074611.4ccc377a@python.org> On Jan 09, 2011, at 08:29 AM, Georg Brandl wrote: >I've now commented out the problematic code -- I'll try to find out more and >maybe ask the Emacs devs, but it's not important enough to hold up a relese. > >BTW, NEWS says "New in version 5.2.0", so if you want to call the release >5.1.1 you have to adapt this; however I'd say there are enough changes to >warrant a minor-version step. I agree. I retired 5.1.1 and moved its items to the 5.2.0 milestone. I've tagged the tree and uploaded both the .el and the tgz file. Thanks for all your great work; I'm sending the announcement momentarily. -Barry -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 836 bytes Desc: not available URL: From skip at pobox.com Sun Jan 9 19:38:40 2011 From: skip at pobox.com (skip at pobox.com) Date: Sun, 9 Jan 2011 12:38:40 -0600 Subject: [Python-mode] Triple quoted string problem Message-ID: <19754.176.399251.164468@montanaro.dyndns.org> I hesitate to open a new bug because this has probably been covered somewhere and I already opened one (sort of) duplicate bug today, but it's hard to tell because there are so many open triple-quoted string bug reports. Using the latest release I created a new file with just a #! line and a doc string: #!/usr/bin/env python """ Maintain the recent "best" price and alert when it remains the best price for a user-defined time. """ When I attempt to fill the docstring's paragraph with the cursor positioned in front of Maintain it zaps the space before '"best"' and fails to actually fill the paragraph: #!/usr/bin/env python """ Maintain the recent"best" price and alert when it remains the best price for a user-defined time. """ If I then move the cursor down a line (point positioned ahead of 'the') and fill again, I get this: #!/usr/bin/env python """ Maintain the recent"best" price and alert when it remains the best price for a user-defined time. """ which is pretty bad considering fill-column is set to 70 in that buffer. This is using XEmacs 21.5.28 on Solaris. On XEmacs 21.4.22 (on Mac OSX) I get somewhat different behavior. There, not sure why, but my fill-column is 76. It formats the entire docstring onto one line: #!/usr/bin/env python """ Maintain the recent"best" price and alert when it remains the best price for a user-defined time. """ In short, I'm not sure that paragraph filling inside triple-quoted strings is any better now than before the release. In fact, it might even be worse overall. :-( Skip From skip at pobox.com Sun Jan 9 19:40:22 2011 From: skip at pobox.com (skip at pobox.com) Date: Sun, 9 Jan 2011 12:40:22 -0600 Subject: [Python-mode] Triple quoted string problem Message-ID: <19754.278.407857.894487@montanaro.dyndns.org> When I attempt to fill the docstring's paragraph with the cursor positioned in front of Maintain it zaps the space before '"best"' and fails to actually fill the paragraph: #!/usr/bin/env python """ Maintain the recent"best" price and alert when it remains the best price for a user-defined time. """ FYI, changing the quoting around the word best from quotation marks to apostrophes results in correct behavior. S From andreas.roehler at online.de Sun Jan 9 20:34:48 2011 From: andreas.roehler at online.de (=?ISO-8859-15?Q?Andreas_R=F6hler?=) Date: Sun, 09 Jan 2011 20:34:48 +0100 Subject: [Python-mode] avoiding edit wars Message-ID: <4D2A0DD8.8010304@online.de> Hi Barry, with respect to bug-fixing discussions last days it might be useful to reflect some rules in order to avoid edit wars. If several developers join interest in a solution, it's fine. However, different persons tend to harbour different opinions, that's normal. So how to make decisions then? Probably you won't have the time to make all. Also voting might not be realistic for the same reason. So delegation is needed. How to delegate? Understood the instrument of assigning a bug to someone in such, having a person in charge not just for writing fixes but taking care for the process until it's committed. Setting the status flags should be part of the job, as it signals proceeding, might call others for action etc. If people don't agree with decisions of the assignee, they should post to him/her, but not toggle the flags themselves. Finally it's your job IMHO to revoke an assignment, if disputes can't be settled otherwise. These understanding seems not common so far. Happy to see things developing fast last days, what's great. Just makes it worthwhile to address upcoming dangers. Thanks all Andreas From barry at python.org Mon Jan 10 19:59:44 2011 From: barry at python.org (Barry Warsaw) Date: Mon, 10 Jan 2011 13:59:44 -0500 Subject: [Python-mode] Triple quoted string problem In-Reply-To: <19754.278.407857.894487@montanaro.dyndns.org> References: <19754.278.407857.894487@montanaro.dyndns.org> Message-ID: <20110110135944.368cf2bc@python.org> On Jan 09, 2011, at 12:40 PM, skip at pobox.com wrote: > When I attempt to fill the docstring's paragraph with the cursor > positioned in front of Maintain it zaps the space before '"best"' and > fails to actually fill the paragraph: > > #!/usr/bin/env python > > """ > Maintain the recent"best" price and alert when it remains > the best price for a user-defined time. > """ > >FYI, changing the quoting around the word best from quotation marks to >apostrophes results in correct behavior. I can confirm both of these on Emacs 23.2.1. Please file a bug. :( -Barry -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 836 bytes Desc: not available URL: From skip at pobox.com Mon Jan 10 20:22:05 2011 From: skip at pobox.com (skip at pobox.com) Date: Mon, 10 Jan 2011 13:22:05 -0600 Subject: [Python-mode] Triple quoted string problem In-Reply-To: <20110110135944.368cf2bc@python.org> References: <19754.278.407857.894487@montanaro.dyndns.org> <20110110135944.368cf2bc@python.org> Message-ID: <19755.23645.159326.141774@montanaro.dyndns.org> Barry> I can confirm both of these on Emacs 23.2.1. Please file a bug. :( https://bugs.launchpad.net/python-mode/+bug/701175 S From barry at python.org Tue Jan 11 01:15:31 2011 From: barry at python.org (Barry Warsaw) Date: Mon, 10 Jan 2011 19:15:31 -0500 Subject: [Python-mode] avoiding edit wars In-Reply-To: <4D2A0DD8.8010304@online.de> References: <4D2A0DD8.8010304@online.de> Message-ID: <20110110191531.34a29fc1@python.org> Hi Andreas, On Jan 09, 2011, at 08:34 PM, Andreas R?hler wrote: >with respect to bug-fixing discussions last days it >might be useful to reflect some rules in order to avoid >edit wars. > >If several developers join interest in a solution, it's >fine. However, different persons tend to harbour >different opinions, that's normal. > >So how to make decisions then? To be honest, we're such a small project that I'd opt for less bureaucracy and more consensus. I think we'll probably end up agreeing 90% of the time, with another 9% where only one person cares. :) In the rare case of disagreement, let's bring the discussion to the mailing list and try to find common ground. If we can't then, to the effect that you still trust me to break the tie, I'm happy to do so. >Happy to see things developing fast last days, what's >great. Just makes it worthwhile to address upcoming >dangers. Yes, it is fantastic all the work you've done and it's great to see Georg getting active too. Makes up for all the slacking I've done lately. :) -Barry -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 836 bytes Desc: not available URL: From andreas.roehler at online.de Tue Jan 11 09:55:28 2011 From: andreas.roehler at online.de (=?ISO-8859-15?Q?Andreas_R=F6hler?=) Date: Tue, 11 Jan 2011 09:55:28 +0100 Subject: [Python-mode] simplified procedure Message-ID: <4D2C1B00.1010501@online.de> Hi Barry, thanks for the merges. With respect to the still considerable amount of reports and a possible speed up of it's treatment, please permit some reflexions, how ease the process: - as for pure typos, whitespace, indent-matters IMHO developers should be permitted to push into the trunk without prior notice. - if funktion is changed, newly introduced, we could agree a simplified procedure, saying a delay of three days, so people may object. - in cases of fundamental change I won't act without your prior consent. So far Andreas PS https://code.launchpad.net/~a-roehler/python-mode/string-to-syntax is still unmerged. It concerns XEmacs only (featurep 'xemacs)..., From barry at python.org Tue Jan 11 16:20:46 2011 From: barry at python.org (Barry Warsaw) Date: Tue, 11 Jan 2011 10:20:46 -0500 Subject: [Python-mode] simplified procedure In-Reply-To: <4D2C1B00.1010501@online.de> References: <4D2C1B00.1010501@online.de> Message-ID: <20110111102046.6ec0555a@python.org> Hi Andreas, On Jan 11, 2011, at 09:55 AM, Andreas R?hler wrote: >With respect to the still considerable amount of >reports and a possible speed up of it's treatment, please >permit some reflexions, how ease the process: > >- as for pure typos, whitespace, indent-matters IMHO > developers should be permitted to push into the trunk > without prior notice. Sure. I think it's fine to JFDI for trivial patches. After all, we have a version control system and post-commit notifications with diffs. I don't think you even need to do a merge proposal for those. >- if funktion is changed, newly introduced, we could > agree a simplified procedure, saying a delay of three > days, so people may object. A merge proposal would be nice, and waiting a few days (perhaps with a ping on email or irc). Three days is probably fine, though be a little more lenient around weekends and holidays. Other than that, if you feel pretty confident about the change and no one responds, JFDI. There will be times when you might not be able to get anyone's attention for various reasons. I'd say that in the above two cases, you should not let that block your progress. Just self-approve the mp and commit. >- in cases of fundamental change I won't act without > your prior consent. Yep, behavior changes should require a higher barrier. A discussion on this mailing list would always be good (before, during, or after merge proposal is submitted). >https://code.launchpad.net/~a-roehler/python-mode/string-to-syntax > >is still unmerged. It concerns XEmacs only (featurep >'xemacs)..., I commented on the mp. Cheers, -Barry P.S. Better to use my @python.org address for this mailing list. :) -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 836 bytes Desc: not available URL: From lists at onerussian.com Tue Jan 11 16:47:53 2011 From: lists at onerussian.com (Yaroslav Halchenko) Date: Tue, 11 Jan 2011 10:47:53 -0500 Subject: [Python-mode] python-mode and ipython.el Message-ID: <20110111154753.GZ27814@onerussian.com> Hi Guys, Somewhat unrelated to the release of python-mode... I wonder if anyone is using python-mode together with ipython as the interpreter... do you use then ipython's ipython.el? My problem is that previously (I think with emacs 22 and snapshots prior 23), when I used python-mode + ipython.el, completions in the python shell were working just fine. Then after some upgrade (sorry, I do not recollect when it happened but may be nearly a year ago) -- completions stopped working. Now I am using emacs 23.2+1-7 on Debian, python shell can't complete even environment names, not to mention attributes of the modules/objects: Using the CPython shell Can't find completion for "nump" [2 times] Can't find completion for "numpy" Can't find completion for "numpy." I just thought to ask here first ;-) -- =------------------------------------------------------------------= Keep in touch www.onerussian.com Yaroslav Halchenko www.ohloh.net/accounts/yarikoptic From lists at onerussian.com Tue Jan 11 17:44:59 2011 From: lists at onerussian.com (Yaroslav Halchenko) Date: Tue, 11 Jan 2011 11:44:59 -0500 Subject: [Python-mode] python-mode and ipython.el In-Reply-To: <20110111154753.GZ27814@onerussian.com> References: <20110111154753.GZ27814@onerussian.com> Message-ID: <20110111164458.GA27814@onerussian.com> nevermind -- debugged situation... problem is inherent to ipython and somewhat non-robustness of ipython.el. FWIW: ipython 0.10 (in Debian sid/squeeze) has issue handling its ad-hoc way to silence it down for some calls: e.g. in fixed 0.10.1: In [1]: print 1 # PYTHON-MODE SILENT 1 while in 0.10: In [1]: print 1 # PYTHON-MODE SILENT ------> print(1 # PYTHON-MODE SILENT) ...: ...: ...: ...: goes on as a quick work-around if someone hits it as well: (setq ipython-completion-command-string "print(';'.join(__IP.Completer.all_completions('%s'))) #PYTHON-MODE SILENT\n") Cheers On Tue, 11 Jan 2011, Yaroslav Halchenko wrote: > Hi Guys, > Somewhat unrelated to the release of python-mode... > I wonder if anyone is using python-mode together with ipython as the > interpreter... do you use then ipython's ipython.el? > My problem is that previously (I think with emacs 22 and snapshots prior 23), > when I used python-mode + ipython.el, completions in the python shell were > working just fine. Then after some upgrade (sorry, I do not recollect when it > happened but may be nearly a year ago) -- completions stopped working. Now I am > using emacs 23.2+1-7 on Debian, python shell can't complete even environment > names, not to mention attributes of the modules/objects: > Using the CPython shell > Can't find completion for "nump" [2 times] > Can't find completion for "numpy" > Can't find completion for "numpy." > I just thought to ask here first ;-) -- =------------------------------------------------------------------= Keep in touch www.onerussian.com Yaroslav Halchenko www.ohloh.net/accounts/yarikoptic From andreas.roehler at easy-emacs.de Tue Jan 11 17:55:44 2011 From: andreas.roehler at easy-emacs.de (=?ISO-8859-15?Q?Andreas_R=F6hler?=) Date: Tue, 11 Jan 2011 17:55:44 +0100 Subject: [Python-mode] c/c++ project management and debugging In-Reply-To: References: <4D0F4058.6050101@gmail.com> <038dfa58-3e80-4c49-bbd0-c1bbb16c41f1@j25g2000vbs.googlegroups.com> <0d3b97e2-c21c-4a83-a8dc-1ba186a5a405@m11g2000vbs.googlegroups.com> <87k4j2x0n3.fsf@kuiper.lan.informatimago.com> <87d3ottiyp.fsf@kuiper.lan.informatimago.com> <87k4iclxye.fsf@kuiper.lan.informatimago.com> Message-ID: <4D2C8B90.2040502@easy-emacs.de> Am 10.01.2011 17:18, schrieb Richard Riley: > Gary writes: > >> Le Wang wrote: >> >>> My opinion of Eclipse aside, generally, when someone argues is >>> because Google results count is xxx, you should seriously >>> question >>> that side of the argument. >> >> I didn't claim it was slow "because Google results count is xxx", I >> claimed that it was slow because that was my experience. Stop trying to >> put words in my "mouth". >> > > Eclipse isn't slow when using it. Well, not really any appreciable > amount slower than any other dekstop GUI editor. And its certainly a lot > more powerful than most if you are a programmer dealing with multiple > languages or wanting a common look and feel IDE for all projects. Mixed > mode in debian is kind of ok with nxhtml, but Java is nigh on impossible > (well, hard work - what is the status with JDEE now?), python is a > confusing mess (multiple python modes floating around) Hi Richard, can't contradict basically, but let me say: python-mode.el at https://launchpad.net/python-mode got some momentum. What about joining the team? In case you join, I'll propose a milestone "python auto-completion-mode" during next weeks. Cheers Andreas -- https://code.launchpad.net/~a-roehler/python-mode/python-mode-components https://code.launchpad.net/s-x-emacs-werkstatt/ : of course the > benefits of Eclipse also introduce some overheads but not ones I feel > are detrimental to any development process. > From georg at python.org Tue Jan 11 19:40:05 2011 From: georg at python.org (Georg Brandl) Date: Tue, 11 Jan 2011 19:40:05 +0100 Subject: [Python-mode] simplified procedure In-Reply-To: <20110111102046.6ec0555a@python.org> References: <4D2C1B00.1010501@online.de> <20110111102046.6ec0555a@python.org> Message-ID: <4D2CA405.8030506@python.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Am 11.01.2011 16:20, schrieb Barry Warsaw: > Hi Andreas, > > On Jan 11, 2011, at 09:55 AM, Andreas R?hler wrote: > >>With respect to the still considerable amount of >>reports and a possible speed up of it's treatment, please >>permit some reflexions, how ease the process: >> >>- as for pure typos, whitespace, indent-matters IMHO >> developers should be permitted to push into the trunk >> without prior notice. > > Sure. I think it's fine to JFDI for trivial patches. After all, we have a > version control system and post-commit notifications with diffs. I don't > think you even need to do a merge proposal for those. I agree -- in fact that's what I've been doing all the time except for the new font-lock faces. >>- if funktion is changed, newly introduced, we could >> agree a simplified procedure, saying a delay of three >> days, so people may object. > > A merge proposal would be nice, and waiting a few days (perhaps with a ping on > email or irc). Three days is probably fine, though be a little more lenient > around weekends and holidays. Other than that, if you feel pretty confident > about the change and no one responds, JFDI. > > There will be times when you might not be able to get anyone's attention for > various reasons. I'd say that in the above two cases, you should not let that > block your progress. Just self-approve the mp and commit. > >>- in cases of fundamental change I won't act without >> your prior consent. > > Yep, behavior changes should require a higher barrier. A discussion on this > mailing list would always be good (before, during, or after merge proposal is > submitted). Not sure if you and Andreas agree what a "fundamental change" or "behavior change" is. Georg -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) iEYEARECAAYFAk0spAQACgkQN9GcIYhpnLCeUgCbBqBC9sC2E6THsJu94miNzgxC /cEAn2B+qlEi9+ynqqpL5axqT1/KUcL5 =L/OX -----END PGP SIGNATURE----- From barry at python.org Tue Jan 11 18:53:26 2011 From: barry at python.org (Barry Warsaw) Date: Tue, 11 Jan 2011 12:53:26 -0500 Subject: [Python-mode] simplified procedure In-Reply-To: <4D2CA405.8030506@python.org> References: <4D2C1B00.1010501@online.de> <20110111102046.6ec0555a@python.org> <4D2CA405.8030506@python.org> Message-ID: <20110111125326.3e9a3dba@python.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On Jan 11, 2011, at 07:40 PM, Georg Brandl wrote: >-----BEGIN PGP SIGNED MESSAGE----- >Am 11.01.2011 16:20, schrieb Barry Warsaw: >> Sure. I think it's fine to JFDI for trivial patches. After all, we have a >> version control system and post-commit notifications with diffs. I don't >> think you even need to do a merge proposal for those. > >I agree -- in fact that's what I've been doing all the time except for the >new font-lock faces. Me too. >> Yep, behavior changes should require a higher barrier. A discussion on this >> mailing list would always be good (before, during, or after merge proposal is >> submitted). > >Not sure if you and Andreas agree what a "fundamental change" or "behavior >change" is. Oh that's easy. If it would confuse me or Guido, it counts. :) - -Barry -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iQIcBAEBCAAGBQJNLJkWAAoJEBJutWOnSwa/AUgP/3ThvROSuJoJkSJaZSuaX9zc 2RZM6grqDKgokLKK3xsnHFGEryJHFBL1IPxmi572FDmm2hHJII0eiR03ROfYr5bS FTN90L0aY0GbWvuJypuVGCYh3L/pGzxA9Ho6QrG3cpM18lb9q3onvlNwdOCjYtVb hTZ2+UQuCBVSk5reeDGjodk99j79CZPrI5Vucy2NnCQIhDTN9IHg5HxOSdUlu79r ivn+9LiLLdWbviNb9RVXS7cCfA6Txd3lOKjdISRAnEV+LQQ3ngaG+VI8M9xDICsw wcoblWpfkT4ntdju0otzL/hTHxR4hW53puj2b63Ictr7EFGC0AEV7mqIDtLxNvSA kLhvURDI/D+zq0cgCB0RGCIxhv0ydFfBANFB1IsIg4yyMaal7u90Kr2jHKjabnhR fg2rfFlwNT/xdF2YHO6sq9ZgNMljzcvEbh0R/z594DTYdvRpK73/og3DLERG3d5G 3g8fCurtqxzQ8RPoi3egN4s0FxZex9A9JMQcqJ//3ym/9+DlUOAFsdOnfFs2HPho f6DBWTOoPi3OD4Aicx/BjysAoaFE0fMYkmA3erwE3N/l6laLMZf8Aj6tX6N5qp10 o5VP0f3N3x2Zy6TwgqYSKZo2Q5a7OGE1CPbWom4TbwGUNilYEBWnus31rVQebLVW sBhf958bgyBG6YbTPgbb =x1ne -----END PGP SIGNATURE----- From skip at pobox.com Wed Jan 12 03:50:34 2011 From: skip at pobox.com (skip at pobox.com) Date: Tue, 11 Jan 2011 20:50:34 -0600 Subject: [Python-mode] [Merge] lp:~a-roehler/python-mode/string-to-syntax into lp:python-mode In-Reply-To: <4D2C934E.3010300@online.de> References: <20110111154940.27543.68076.codereview@wampee.canonical.com> <4D2C934E.3010300@online.de> Message-ID: <19757.5882.60554.927604@montanaro.dyndns.org> Sorry this got all garbled, however... Andreas> diff python-mode.el.THIS python-mode.el.BASE Andreas> 447c447 Andreas> < (syntax (parse-partial-sexp (point-min) (point)))) Andreas> --- >> (syntax (syntax-ppss))) Andreas> 463c463 Andreas> < (unless (eq 'string (syntax-ppss-context (parse-partial-sexp Andreas> (point-min) (point)))) The call to syntax-ppss-context probably has to be replaced by something XEmacs-compatible too. Apologies if I've not read Andreas's diff correctly. Skip From andreas.roehler at online.de Wed Jan 12 09:34:03 2011 From: andreas.roehler at online.de (=?ISO-8859-1?Q?Andreas_R=F6hler?=) Date: Wed, 12 Jan 2011 09:34:03 +0100 Subject: [Python-mode] [Merge] lp:~a-roehler/python-mode/string-to-syntax into lp:python-mode In-Reply-To: <19757.5882.60554.927604@montanaro.dyndns.org> References: <20110111154940.27543.68076.codereview@wampee.canonical.com> <4D2C934E.3010300@online.de> <19757.5882.60554.927604@montanaro.dyndns.org> Message-ID: <4D2D677B.1070301@online.de> Am 12.01.2011 03:50, schrieb skip at pobox.com: > > Sorry this got all garbled, however... > > Andreas> diff python-mode.el.THIS python-mode.el.BASE > Andreas> 447c447 > Andreas> < (syntax (parse-partial-sexp (point-min) (point)))) > Andreas> --- > >> (syntax (syntax-ppss))) > Andreas> 463c463 > Andreas> < (unless (eq 'string (syntax-ppss-context (parse-partial-sexp > Andreas> (point-min) (point)))) > > The call to syntax-ppss-context probably has to be replaced by something > XEmacs-compatible too. > > Apologies if I've not read Andreas's diff correctly. > > Skip > Hi Skip, thanks. See I still have to deal with `syntax-ppss-context' unknown to XEmacs - which is not a surprise... Allthough I'm confident solving this within a reasonable time, please permit some considerations concerning XEmacs compatibility though. Unfortunatly the tqs-syntax matter was not just copy-and-paste as Georg assumed :-) Tweaking that in a different environment required some effort. And still we have tqs-bugs, just no valid report for it AFAIS. As the tqs-handling is crucial for any python-mode, consider that a task of first order. Python.el seems not to show this bug, copy-and-paste indeed might solve it here once and for all. But XEmacs compatibility is broken than. As XEmacs has proclaimed it's intend to merge up with GNU code, that may pay for a while. Bluntly said: Beside of the pps issue going to be solved, don't foresee keeping a fully compatible python-mode. Trying that, I'm afraid we will go out of business alltogether. A solution might be keeping an XEmacs compatible separate version. Would mean another split and python-mode version around... :( OTOH: we could proceed then much faster with the GNU-branch, having again a reliable, maybe most advanced python-mode. Also, when fixing a bug there, we always may have a look, if its possible similar inside existing XE branch. Having a running XEamcs still, I'd be willing to take part. Well, just addressing the matter Andreas From barry at python.org Wed Jan 12 00:32:18 2011 From: barry at python.org (Barry Warsaw) Date: Tue, 11 Jan 2011 18:32:18 -0500 Subject: [Python-mode] [Merge] lp:~a-roehler/python-mode/string-to-syntax into lp:python-mode In-Reply-To: <4D2D677B.1070301@online.de> References: <20110111154940.27543.68076.codereview@wampee.canonical.com> <4D2C934E.3010300@online.de> <19757.5882.60554.927604@montanaro.dyndns.org> <4D2D677B.1070301@online.de> Message-ID: <20110111183218.4cf33fad@python.org> On Jan 12, 2011, at 09:34 AM, Andreas R?hler wrote: >Bluntly said: Beside of the pps issue going to be solved, don't foresee >keeping a fully compatible python-mode. Trying that, I'm afraid we will go >out of business alltogether. > >A solution might be keeping an XEmacs compatible separate version. Would mean >another split and python-mode version around... :( Which would effectively kill XEmacs support forever. If we were to fork, I suspect that fork would die a quick death. Better to keep one version even if XEmacs support is temporarily broken. If we don't have enough XEmacs testers or contributors to ensure it works before a release, we'll just to have to make a lesser guarantee and hope for patches from interested parties (hi Skip :). Speaking of which, I will wait until Skip gives me the green light and then I will release a 5.2.1 that fixes the XEmacs support. Just let me know. -Barry -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 836 bytes Desc: not available URL: From skip at pobox.com Wed Jan 12 14:19:45 2011 From: skip at pobox.com (skip at pobox.com) Date: Wed, 12 Jan 2011 07:19:45 -0600 Subject: [Python-mode] string-to-syntax for XEmacs 21.4? (fwd) Message-ID: <19757.43633.996732.678262@montanaro.dyndns.org> Passing this along from Stephen Turnbull on the XEmacs list... Skip -------------- next part -------------- An embedded message was scrubbed... From: "Stephen J. Turnbull" Subject: Re: string-to-syntax for XEmacs 21.4? Date: Tue, 11 Jan 2011 17:22:23 +0900 Size: 3537 URL: From skip at pobox.com Wed Jan 12 14:16:03 2011 From: skip at pobox.com (skip at pobox.com) Date: Wed, 12 Jan 2011 07:16:03 -0600 Subject: [Python-mode] [Merge] lp:~a-roehler/python-mode/string-to-syntax into lp:python-mode In-Reply-To: <4D2D677B.1070301@online.de> References: <20110111154940.27543.68076.codereview@wampee.canonical.com> <4D2C934E.3010300@online.de> <19757.5882.60554.927604@montanaro.dyndns.org> <4D2D677B.1070301@online.de> Message-ID: <19757.43411.579406.917370@montanaro.dyndns.org> Andreas> As XEmacs has proclaimed it's intend to merge up with GNU code, Andreas> that may pay for a while. I wouldn't hold my breath. As Barry indicated, XEmacs doesn't seem to be progressing. I haven't seen a release of any kind for quite awhile. Andreas> A solution might be keeping an XEmacs compatible separate Andreas> version. Would mean another split and python-mode version Andreas> around... :( Andreas> OTOH: we could proceed then much faster with the GNU-branch, Andreas> having again a reliable, maybe most advanced python-mode. Why not just refer to the last version which was XEmacs-friendly on the Launchpad download site? I think 5.1.0. Modify 5.2.0 and greater if it's loaded in an XEmacs session that certain stuff won't work until such time in the future that it does work in that environment again. Skip From barry at python.org Thu Jan 13 02:23:19 2011 From: barry at python.org (Barry Warsaw) Date: Wed, 12 Jan 2011 20:23:19 -0500 Subject: [Python-mode] [Merge] lp:~a-roehler/python-mode/string-to-syntax into lp:python-mode In-Reply-To: <19757.43411.579406.917370@montanaro.dyndns.org> References: <20110111154940.27543.68076.codereview@wampee.canonical.com> <4D2C934E.3010300@online.de> <19757.5882.60554.927604@montanaro.dyndns.org> <4D2D677B.1070301@online.de> <19757.43411.579406.917370@montanaro.dyndns.org> Message-ID: <20110112202319.573e25f3@python.org> On Jan 12, 2011, at 07:16 AM, skip at pobox.com wrote: >Why not just refer to the last version which was XEmacs-friendly on the >Launchpad download site? I think 5.1.0. Modify 5.2.0 and greater if it's >loaded in an XEmacs session that certain stuff won't work until such time in >the future that it does work in that environment again. There doesn't seem to be a way to have the project page show downloads from anything but the current release. However, old releases are still there: https://launchpad.net/python-mode/+download Still, I think it would ultimately be best if we could continue to support XEmacs for basic editing. We'll have to rely on XEmacs users to test things, but I'm also happy waiting for Skip (or whomever) to give the green light for XEmacs compatibility before I announce a new release. I think it would also be okay if some reduced functionality is allowed to creep in, but let's be explicit about it. I.e. the mode should not crash in XEmacs, and basic editing should always work, but it would be okay if some Emacs-only feature were supported with no equivalent in XEmacs. But maybe there will come a point where XEmacs (or our support of it) just has to be declared dead. I dunno, and I don't want to make that decision, so as long as Skip's still using it I think we should try to continue to support it. -Barry -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 836 bytes Desc: not available URL: From skip at pobox.com Thu Jan 13 21:05:51 2011 From: skip at pobox.com (skip at pobox.com) Date: Thu, 13 Jan 2011 14:05:51 -0600 Subject: [Python-mode] confusion about py-string-to-syntax def Message-ID: <19759.23327.372671.650765@montanaro.dyndns.org> I'm trying to get the latest python-mode.el to compile cleanly. I have this definition: ;; Skip's XE workaround (if (fboundp 'string-to-syntax) (defalias 'py-string-to-syntax string-to-syntax) (defun py-string-to-syntax (s) (cond ((equal s "|") '(15)) ((equal s "_") '(3)) (t (error "Unhandled string: %s" s)))) ) and get this output from byte-compile-file: Compiling file /Users/skip/src/python-mode/python-mode.el at Thu Jan 13 14:03:29 2011 ** attempt to inline py-string-to-syntax before it was defined ** attempt to inline py-string-to-syntax before it was defined ** attempt to inline py-string-to-syntax before it was defined ** attempt to inline py-string-to-syntax before it was defined ** attempt to inline py-string-to-syntax before it was defined While compiling toplevel forms: ** attempt to inline py-string-to-syntax before it was defined Why? Is that an error? I do get a .elc file so I sort of assume it's just a warning. Skip From andreas.roehler at online.de Thu Jan 13 22:09:52 2011 From: andreas.roehler at online.de (=?ISO-8859-1?Q?Andreas_R=F6hler?=) Date: Thu, 13 Jan 2011 22:09:52 +0100 Subject: [Python-mode] confusion about py-string-to-syntax def In-Reply-To: <19759.23327.372671.650765@montanaro.dyndns.org> References: <19759.23327.372671.650765@montanaro.dyndns.org> Message-ID: <4D2F6A20.4000906@online.de> Am 13.01.2011 21:05, schrieb skip at pobox.com: > I'm trying to get the latest python-mode.el to compile cleanly. I have this > definition: > > ;; Skip's XE workaround > (if (fboundp 'string-to-syntax) > (defalias 'py-string-to-syntax string-to-syntax) > (defun py-string-to-syntax (s) > (cond > ((equal s "|") '(15)) > ((equal s "_") '(3)) > (t (error "Unhandled string: %s" s)))) > ) > Thanks, though my taste is still the other way around: as soon as XEmacs merges up to GNU code, would should drop our stuff, considered a possible a bug-source than. With the use of a aliased function I'm afraid, we have the complexity and bug source just now. I'll be patient and look, should someone want to write that in. Just rather not me :-) Let's go on Andreas From barry at python.org Thu Jan 13 22:13:18 2011 From: barry at python.org (Barry Warsaw) Date: Thu, 13 Jan 2011 16:13:18 -0500 Subject: [Python-mode] confusion about py-string-to-syntax def In-Reply-To: <4D2F6A20.4000906@online.de> References: <19759.23327.372671.650765@montanaro.dyndns.org> <4D2F6A20.4000906@online.de> Message-ID: <20110113161318.7e54ae2e@python.org> On Jan 13, 2011, at 10:09 PM, Andreas R?hler wrote: >Am 13.01.2011 21:05, schrieb skip at pobox.com: >> I'm trying to get the latest python-mode.el to compile cleanly. I have this >> definition: >> >> ;; Skip's XE workaround >> (if (fboundp 'string-to-syntax) >> (defalias 'py-string-to-syntax string-to-syntax) >> (defun py-string-to-syntax (s) >> (cond >> ((equal s "|") '(15)) >> ((equal s "_") '(3)) >> (t (error "Unhandled string: %s" s)))) >> ) >> > >though my taste is still the other way around: > >as soon as XEmacs merges up to GNU code, would should drop our stuff, considered a possible a bug-source than. > >With the use of a aliased function I'm afraid, we have the complexity and bug source just now. > >I'll be patient and look, should someone want to write that in. >Just rather not me :-) > >Let's go on As I said, you're doing the work, and this is internal stuff, so it's your call. :) -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 836 bytes Desc: not available URL: From andreas.roehler at online.de Fri Jan 14 08:15:07 2011 From: andreas.roehler at online.de (=?ISO-8859-1?Q?Andreas_R=F6hler?=) Date: Fri, 14 Jan 2011 08:15:07 +0100 Subject: [Python-mode] confusion about py-string-to-syntax def In-Reply-To: <19759.27548.929044.818134@montanaro.dyndns.org> References: <19759.23327.372671.650765@montanaro.dyndns.org> <4D2F6A20.4000906@online.de> <20110113161318.7e54ae2e@python.org> <19759.27548.929044.818134@montanaro.dyndns.org> Message-ID: <4D2FF7FB.3010908@online.de> Am 13.01.2011 22:16, schrieb skip at pobox.com: > >>> I'm trying to get the latest python-mode.el to compile cleanly. > > Neither of you answered this question. :-) How do I get those warnings to > go away? > > Skip > Hi Skip, seems you introduced a bug. Why not use the trunk? BTW all the "py-"-prefix and defalias considerations here are missing the point IMHO in such, as if in further futures XEmacs should provide this symbol, the compiler will tell..."defined a second time". Until then, please let us stay as much as possible with the existing code, as tqs-syntax-setting is known to work elsewhere. If extra stuff is introduced in this context, debugging syntax will be harder. What about removing remaining compiler warnings, which are not functional AFAIS? For example introducing some defvars to silence the compiler in these cases. Thanks BTW having brought the compiling question to attention here. Andreas From skip at pobox.com Fri Jan 14 15:07:59 2011 From: skip at pobox.com (skip at pobox.com) Date: Fri, 14 Jan 2011 08:07:59 -0600 Subject: [Python-mode] confusion about py-string-to-syntax def In-Reply-To: <4D2FF7FB.3010908@online.de> References: <19759.23327.372671.650765@montanaro.dyndns.org> <4D2F6A20.4000906@online.de> <20110113161318.7e54ae2e@python.org> <19759.27548.929044.818134@montanaro.dyndns.org> <4D2FF7FB.3010908@online.de> Message-ID: <19760.22719.390803.550212@montanaro.dyndns.org> Andreas> seems you introduced a bug. Why not use the trunk? I would if I could. I have been merging trunk to my branch. How do I swap my (mostly dead) branch for trunk? Guys, I generally find DVCS very difficult to use. They don't fit my brain at all. (I fear for the day when the Python source tree switches to Mercurial. I don't think I will be able to function at all.) That said, I do like branching and use it all the time with Subversion and CVS. Help me figure out how to use bzr, git, hg, etc in a CVS/Subversion-like way and you'll have a friend for life. Andreas> BTW all the "py-"-prefix and defalias considerations here are Andreas> missing the point IMHO in such, as if in further futures XEmacs Andreas> should provide this symbol, the compiler will tell..."defined a Andreas> second time". I thought Barry's note about not polluting the global namespace was correct. My crippled string-to-syntax will only work for the cases needed by python-mode. I think you need to create py-string-to-syntax and refer to it. Otherwise you run the risk of making some other package blow up. Andreas> Until then, please let us stay as much as possible with the Andreas> existing code, as tqs-syntax-setting is known to work Andreas> elsewhere. What is tqs-syntax-setting? Andreas> What about removing remaining compiler warnings, which are not Andreas> functional AFAIS? For example introducing some defvars to Andreas> silence the compiler in these cases. I have no idea how to do that. Skip From barry at python.org Fri Jan 14 05:21:16 2011 From: barry at python.org (Barry Warsaw) Date: Thu, 13 Jan 2011 23:21:16 -0500 Subject: [Python-mode] confusion about py-string-to-syntax def In-Reply-To: <19760.22719.390803.550212@montanaro.dyndns.org> References: <19759.23327.372671.650765@montanaro.dyndns.org> <4D2F6A20.4000906@online.de> <20110113161318.7e54ae2e@python.org> <19759.27548.929044.818134@montanaro.dyndns.org> <4D2FF7FB.3010908@online.de> <19760.22719.390803.550212@montanaro.dyndns.org> Message-ID: <20110113232116.0c8f9107@python.org> On Jan 14, 2011, at 08:07 AM, skip at pobox.com wrote: >I would if I could. I have been merging trunk to my branch. How do I swap >my (mostly dead) branch for trunk? > >Guys, I generally find DVCS very difficult to use. They don't fit my brain >at all. (I fear for the day when the Python source tree switches to >Mercurial. I don't think I will be able to function at all.) That said, I >do like branching and use it all the time with Subversion and CVS. Help me >figure out how to use bzr, git, hg, etc in a CVS/Subversion-like way and >you'll have a friend for life. Skip, you can use Bazaar essential the same way you use Subversion but doing what's called a "lightweight checkout". Just do: $ bzr co lp:python-mode Then, 'bzr commit' in the python-mode directory will do exactly like 'svn commit' in that it will immediately change the state of the branch on the server, so you need to be on the net, and your local working directory needs to be up-to-date. More details available here: http://wiki.bazaar.canonical.com/CheckoutTutorial -Barry -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 836 bytes Desc: not available URL: From andreas.roehler at online.de Fri Jan 14 22:34:26 2011 From: andreas.roehler at online.de (=?ISO-8859-1?Q?Andreas_R=F6hler?=) Date: Fri, 14 Jan 2011 22:34:26 +0100 Subject: [Python-mode] confusion about py-string-to-syntax def In-Reply-To: <19760.22719.390803.550212@montanaro.dyndns.org> References: <19759.23327.372671.650765@montanaro.dyndns.org> <4D2F6A20.4000906@online.de> <20110113161318.7e54ae2e@python.org> <19759.27548.929044.818134@montanaro.dyndns.org> <4D2FF7FB.3010908@online.de> <19760.22719.390803.550212@montanaro.dyndns.org> Message-ID: <4D30C162.4030001@online.de> [ ... ] > What is tqs-syntax-setting? Meant: Defining the syntax for the triple-quoted-string. From v+python at g.nevcal.com Sat Jan 15 06:49:20 2011 From: v+python at g.nevcal.com (Glenn Linderman) Date: Fri, 14 Jan 2011 21:49:20 -0800 Subject: [Python-mode] bug? Message-ID: <4D313560.4070403@g.nevcal.com> python.el all of a sudden started acting weird... putting in "real" TABs, and not positioning the cursor properly, so I decided maybe I should finally get off my duff and switch to python-mode.el -- so it doesn't put in "real" TABs, but it also was sometimes not positioning the cursor properly :( I finally figured out the cause, but not a cure... I had a large block comment string and above that python-mode works, below it does not. Now in trying to reproduce this to report it, I tried a smaller case, but it works! """ A big block comment like this doesn't seem to throw off the indentation """ The sad part, then, is that the effect is string content dependent! Maybe it has something to do with single quote stuff inside triple quote stuff? Well, maybe. I had 2.5 such. So here is a minimal test case: """ " """ def foo( bar ): _ # cursor stays at left margin instead of indenting. Is this something that is fixable? I didn't try triple single quotes containing unbalanced single quotes or mixing the type of quotes, but those are things that should be tested too, given this failure. It really shouldn't matter what is inside the triple quotes. Before I figured out what the problem was related to, I experienced some bizarre behavior with python.el (but not with python-mode.el, but I don't know what triggered it, to try again), where with the unbalanced strings, it was displaying some code as code, but then after point somewhere (next line) was displaying a block in brown as if it were a string. I thought I had accidentally hit a key I didn't know what it did and changed some setting in python.el that I didn't know about (which is most of them).... it was probably related to this issue, however. And, sorry, I don't know yet how to search for preexisting problems and reported bugs yet, or where to report them, but I found this list and joined it, thinking I'd be asking for help changing configuration settings from "goofy" to "normal", but in making a test case to report, came to a better understanding of the bug, enough to think it is one. Glenn From barry at python.org Sat Jan 15 16:49:13 2011 From: barry at python.org (Barry Warsaw) Date: Sat, 15 Jan 2011 10:49:13 -0500 Subject: [Python-mode] bug? In-Reply-To: <4D313560.4070403@g.nevcal.com> References: <4D313560.4070403@g.nevcal.com> Message-ID: <20110115104913.452a1934@python.org> On Jan 14, 2011, at 09:49 PM, Glenn Linderman wrote: >So here is a minimal test case: > > >""" >" >""" > >def foo( bar ): >_ # cursor stays at left margin instead of indenting. Confirmed with r390 of python-mode.el. It's definitely that embedded double quote. Change it to a single quote and indentation works just fine. I know Andreas has been working hard in this area for the past week or so, so I'll let him follow up. I'm not filing this as a bug, but if you look at https://bugs.launchpad.net/python-mode you'll see several tqs related problems (most are fix committed). -Barry P.S. Welcome to the list! -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 836 bytes Desc: not available URL: From andreas.roehler at online.de Mon Jan 17 13:00:17 2011 From: andreas.roehler at online.de (=?ISO-8859-1?Q?Andreas_R=F6hler?=) Date: Mon, 17 Jan 2011 13:00:17 +0100 Subject: [Python-mode] bug? In-Reply-To: <20110115104913.452a1934@python.org> References: <4D313560.4070403@g.nevcal.com> <20110115104913.452a1934@python.org> Message-ID: <4D342F51.4020709@online.de> Am 15.01.2011 16:49, schrieb Barry Warsaw: > On Jan 14, 2011, at 09:49 PM, Glenn Linderman wrote: > >> So here is a minimal test case: >> >> >> """ >> " >> """ >> >> def foo( bar ): >> _ # cursor stays at left margin instead of indenting. > > Confirmed with r390 of python-mode.el. It's definitely that embedded double > quote. Change it to a single quote and indentation works just fine. > > I know Andreas has been working hard in this area for the past week or so, so > I'll let him follow up. I'm not filing this as a bug, but if you look at > > https://bugs.launchpad.net/python-mode > > you'll see several tqs related problems (most are fix committed). > > -Barry > > P.S. Welcome to the list! > Hi Barry, gladly announce: just checked in a syntax independend string parser with branch `paragraph-fill-warts', addressing a similar bug. A syntax independend parser delivers much more BTW than this workaround ... :-) Beside fixing/re-designing `py-fill-paragraph' `py-fill-string' based on the new parser, a couple of new functions are available. Made an extract from thing-at-point-utils.el, called `triplequoted.el' Also delivering files needed by resp. holding the parser. The full stuff is at https://code.launchpad.net/s-x-emacs-werkstatt/ RATIONALE of re-design: When detecting if inside a triple-quoted-string etc., the borders of the object are already known in this course. Which might be given to fill the string... Available forms for example: `ar-triplequoted-atpt' - finds triplequoted strings under cursor `ar-bounds-of-triplequoted-atpt' ... `ar-triplequoted-dq-atpt' - triplequoted strings using doublequotes ... `ar-triplequoted-sq-atpt' - triplequoted strings using singlequotes ... `ar-quoted-atpt' ... `ar-doublequoted-atpt' ... `ar-singlequoted-atpt' ... Status: experimental, Remaining/new BUG :( error message when loading: "Error in menu-bar-update-hook: (wrong-type-argument stringp nil)" Comments welcome Enjoy Andreas -- https://code.launchpad.net/~a-roehler/python-mode/python-mode-components https://code.launchpad.net/s-x-emacs-werkstatt/ From skip at pobox.com Mon Jan 17 13:53:08 2011 From: skip at pobox.com (skip at pobox.com) Date: Mon, 17 Jan 2011 06:53:08 -0600 Subject: [Python-mode] Version? Message-ID: <19764.15284.385479.636334@montanaro.dyndns.org> I have a branch. According to bzr diff it's identical to lp:python-mode python-mode% bzr diff http://bazaar.launchpad.net/~python-mode-devs/python-mode/python-mode/python-mode.el python-mode.el python-mode% yet the version in my copy of the code is not 5.2.0: (defconst py-version "5.0.0+" "`python-mode' version number.") and the copyright/author info doesn't seem up-to-date: ;; Copyright (C) 1992,1993,1994 Tim Peters ;; Author: 2003-2008 https://launchpad.net/python-mode ;; 1995-2002 Barry A. Warsaw ;; 1992-1994 Tim Peters ;; Maintainer: python-mode at python.org ;; Created: Feb 1992 ;; Keywords: python languages oop What am I missing? Skip From skip at pobox.com Mon Jan 17 13:56:04 2011 From: skip at pobox.com (skip at pobox.com) Date: Mon, 17 Jan 2011 06:56:04 -0600 Subject: [Python-mode] Version? Message-ID: <19764.15460.792228.475648@montanaro.dyndns.org> > I have a branch. According to bzr diff it's identical to lp:python-mode > > python-mode% bzr diff http://bazaar.launchpad.net/~python-mode-devs/python-mode/python-mode/python-mode.el python-mode.el > python-mode% One other thing. It doesn't byte compile for me in XEmacs: Compiling file /Users/skip/src/python-mode/python-mode.el at Mon Jan 17 06:55:12 2011 !! Symbol's function definition is void ((string-to-syntax)) What version am I suppose to be using to test to see if it works under XEmacs? S From andreas.roehler at online.de Mon Jan 17 18:43:05 2011 From: andreas.roehler at online.de (=?ISO-8859-1?Q?Andreas_R=F6hler?=) Date: Mon, 17 Jan 2011 18:43:05 +0100 Subject: [Python-mode] Version? In-Reply-To: <19764.15284.385479.636334@montanaro.dyndns.org> References: <19764.15284.385479.636334@montanaro.dyndns.org> Message-ID: <4D347FA9.4080305@online.de> Am 17.01.2011 13:53, schrieb skip at pobox.com: > I have a branch. According to bzr diff it's identical to lp:python-mode > > python-mode% bzr diff http://bazaar.launchpad.net/~python-mode-devs/python-mode/python-mode/python-mode.el python-mode.el > python-mode% Seems bazaar diff fails here. bzr branch lp:python-mode should deliver the trunk Later do bzr pull from inside the dir to update your local from the trunk Should avoid also the compile error reported in your other mail. HTH Andreas > > yet the version in my copy of the code is not 5.2.0: > > (defconst py-version "5.0.0+" > "`python-mode' version number.") > > and the copyright/author info doesn't seem up-to-date: > > ;; Copyright (C) 1992,1993,1994 Tim Peters > > ;; Author: 2003-2008 https://launchpad.net/python-mode > ;; 1995-2002 Barry A. Warsaw > ;; 1992-1994 Tim Peters > ;; Maintainer: python-mode at python.org > ;; Created: Feb 1992 > ;; Keywords: python languages oop > > What am I missing? > > Skip From skip at pobox.com Mon Jan 17 18:53:44 2011 From: skip at pobox.com (skip at pobox.com) Date: Mon, 17 Jan 2011 11:53:44 -0600 Subject: [Python-mode] Version? In-Reply-To: <4D347FA9.4080305@online.de> References: <19764.15284.385479.636334@montanaro.dyndns.org> <4D347FA9.4080305@online.de> Message-ID: <19764.33320.520425.898060@montanaro.dyndns.org> Andreas> Seems bazaar diff fails here. Andreas> bzr branch lp:python-mode Andreas> should deliver the trunk I'm inside my python-mode sandbox: % bzr branch lp:python-mode Branched 390 revision(s). python-mode% bzr status unknown: python-mode/ python-mode.elc It creates a whole other tree. I don't want an explosion of sandboxes. Can't I switch between different branches somehow? This is perhaps a small point for this, because I can actually get away with deleting my stuff completely and switching to lp:python-mode. For more complex projects though, I should be able to switch between branches. I want the equivalent of the cvs and svn commands cvs up -r some-other-branch svn up -r some-other-branch Is this not possible with bazaar? Skip From andreas.roehler at online.de Mon Jan 17 19:20:17 2011 From: andreas.roehler at online.de (=?ISO-8859-1?Q?Andreas_R=F6hler?=) Date: Mon, 17 Jan 2011 19:20:17 +0100 Subject: [Python-mode] Version? In-Reply-To: <19764.33320.520425.898060@montanaro.dyndns.org> References: <19764.15284.385479.636334@montanaro.dyndns.org> <4D347FA9.4080305@online.de> <19764.33320.520425.898060@montanaro.dyndns.org> Message-ID: <4D348861.2090109@online.de> Am 17.01.2011 18:53, schrieb skip at pobox.com: > > Andreas> Seems bazaar diff fails here. > > Andreas> bzr branch lp:python-mode > > Andreas> should deliver the trunk > > I'm inside my python-mode sandbox: > > % bzr branch lp:python-mode > Branched 390 revision(s). > python-mode% bzr status > unknown: > python-mode/ > python-mode.elc > > It creates a whole other tree. I don't want an explosion of sandboxes. Looks like you branched a repo in a repo A solution is to start from some empty place again. bzr branch lp:python-mode creates a dir python-mode > Can't I switch between different branches somehow? Sure. Depends what you want to do. > > This is perhaps a small point for this, because I can actually get away with > deleting my stuff completely and switching to lp:python-mode. For more > complex projects though, I should be able to switch between branches. I > want the equivalent of the cvs and svn commands > > cvs up -r some-other-branch > svn up -r some-other-branch > > Is this not possible with bazaar? with bazaar you may simply copy locally cp -pur source new or push a branch at some distant place bzr push lp:~/python-mode/blah-and-blub > > Skip > From skip at pobox.com Mon Jan 17 20:51:32 2011 From: skip at pobox.com (skip at pobox.com) Date: Mon, 17 Jan 2011 13:51:32 -0600 Subject: [Python-mode] Still broken Message-ID: <19764.40388.244645.695965@montanaro.dyndns.org> I moved ~/src/python-mode out of the way, then from ~/src I executed bzr co lp:python-mode I verified that it says I have version 5.2.0: (defconst py-version "5.2.0" "`python-mode' version number.") Byte compilation still fails (in a fresh XEmacs session): Compiling file /Users/skip/src/python-mode/python-mode.el at Mon Jan 17 13:50:21 2011 !! Symbol's function definition is void ((string-to-syntax)) Skip From andreas.roehler at online.de Tue Jan 18 08:20:08 2011 From: andreas.roehler at online.de (=?ISO-8859-1?Q?Andreas_R=F6hler?=) Date: Tue, 18 Jan 2011 08:20:08 +0100 Subject: [Python-mode] Still broken In-Reply-To: <19764.40388.244645.695965@montanaro.dyndns.org> References: <19764.40388.244645.695965@montanaro.dyndns.org> Message-ID: <4D353F28.10500@online.de> Am 17.01.2011 20:51, schrieb skip at pobox.com: > I moved ~/src/python-mode out of the way, then from ~/src I executed > > bzr co lp:python-mode > > I verified that it says I have version 5.2.0: > > (defconst py-version "5.2.0" > "`python-mode' version number.") > > Byte compilation still fails (in a fresh XEmacs session): > > Compiling file /Users/skip/src/python-mode/python-mode.el at Mon Jan 17 13:50:21 2011 > !! Symbol's function definition is void ((string-to-syntax)) > > Skip > _______________________________________________ Hi Skip, solution for XEmacs 21.5 at least was, evaling the file before compiling it. Please do a "bzr pull" before anyway, as fboundp got replaced by functionp HTH Andreas From andreas.roehler at online.de Fri Jan 28 18:39:45 2011 From: andreas.roehler at online.de (=?UTF-8?B?QW5kcmVhcyBSw7ZobGVy?=) Date: Fri, 28 Jan 2011 18:39:45 +0100 Subject: [Python-mode] [Bug 637955] Re: py-previous-statement fails In-Reply-To: <20101014111339.24274.4465.launchpad@potassium.ubuntu.com> References: <20100914110848.8730.99566.malonedeb@wampee.canonical.com> <20101014111339.24274.4465.launchpad@potassium.ubuntu.com> Message-ID: <4D42FF61.5020904@online.de> Am 14.10.2010 13:13, schrieb Andreas Roehler: > ** Changed in: python-mode > Assignee: (unassigned) => Andreas Roehler (a-roehler) > Hi Barry, AFAIS it's gone in the trunk now. Could you check it again, so it may be closed? Thanks Andreas From barry at python.org Fri Jan 28 19:19:11 2011 From: barry at python.org (Barry Warsaw) Date: Fri, 28 Jan 2011 13:19:11 -0500 Subject: [Python-mode] [Bug 637955] Re: py-previous-statement fails In-Reply-To: <4D42FF61.5020904@online.de> References: <20100914110848.8730.99566.malonedeb@wampee.canonical.com> <20101014111339.24274.4465.launchpad@potassium.ubuntu.com> <4D42FF61.5020904@online.de> Message-ID: <20110128131911.2329b92d@python.org> On Jan 28, 2011, at 06:39 PM, Andreas R?hler wrote: >Am 14.10.2010 13:13, schrieb Andreas Roehler: >> ** Changed in: python-mode >> Assignee: (unassigned) => Andreas Roehler (a-roehler) >> > >Hi Barry, > >AFAIS it's gone in the trunk now. > >Could you check it again, so it may be closed? Works for me. Is it time for a 5.2.1 release? -Barry -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 836 bytes Desc: not available URL: From andreas.roehler at online.de Fri Jan 28 22:56:07 2011 From: andreas.roehler at online.de (=?ISO-8859-15?Q?Andreas_R=F6hler?=) Date: Fri, 28 Jan 2011 22:56:07 +0100 Subject: [Python-mode] upcoming release Message-ID: <4D433B77.9030602@online.de> Hi Barry, enabling XEmacs' handling of triple-quoted-strings fixing bugs known for now seems an interesting item from my perspective. paragraph-fill-warts branch should enable this. https://code.launchpad.net/~a-roehler/python-mode/paragraph-fill-warts It comes with a lot of utilities though, some required, some just part of the tool-box, where singling-out the required here is possible. I'm hesitating to propose that for general release, as people might be scared by the material, which is just partly python-related. OTOH, what I'm promessing: it pays. These utilities will fasten up editing, python-mode and all other. What about to release a thus experimental brunch for XEmacs users first, while it will work for all? Andreas From barry at python.org Fri Jan 28 23:09:09 2011 From: barry at python.org (Barry Warsaw) Date: Fri, 28 Jan 2011 17:09:09 -0500 Subject: [Python-mode] upcoming release In-Reply-To: <4D433B77.9030602@online.de> References: <4D433B77.9030602@online.de> Message-ID: <20110128170909.75a5cd8f@python.org> On Jan 28, 2011, at 10:56 PM, Andreas R?hler wrote: >enabling XEmacs' handling of triple-quoted-strings fixing bugs known for now >seems an interesting item from my perspective. paragraph-fill-warts branch >should enable this. >https://code.launchpad.net/~a-roehler/python-mode/paragraph-fill-warts It >comes with a lot of utilities though, some required, some just part of the >tool-box, where singling-out the required here is possible. I'm hesitating >to propose that for general release, as people might be scared by the >material, which is just partly python-related. OTOH, what I'm promessing: it >pays. These utilities will fasten up editing, python-mode and all other. >What about to release a thus experimental brunch for XEmacs users first, >while it will work for all? Andreas Andreas, as always, thanks for your hard work on python-mode! It's very much appreciated. I've merged your branch and will play with it over the weekend. I'm going to leave it to Skip to verify the XEmacs compatibility issues (Skip please let us know if you need help getting Andreas's branch). python-mode.el has always been self-contained, meaning people can easily download or copy one file and get great Python support in Emacs. Requiring your utilities changes that, and can make it harder for some folks to adopt python-mode.el. I'm not saying that necessarily means it can't be done, but we do have to think about the ramifications. I'd like to get other folks thoughts on that. OTOH, I encourage you to get your code into upstream Emacs and XEmacs. That would certainly make our lives easy again. :) Do you think it would be possible and easy to pull out just the parts that python-mode.el needs and include those in that file? If not, then what about making sure python-mode.el gracefully degrades when those extra files aren't there? By that I mean, if someone does not have your new utilities, python-mode.el should at least work as well as it does currently. python-mode.el should then take advantage of your utilities if they're available. Thoughts? -Barry -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 836 bytes Desc: not available URL: From andreas.roehler at online.de Sat Jan 29 10:55:57 2011 From: andreas.roehler at online.de (=?ISO-8859-1?Q?Andreas_R=F6hler?=) Date: Sat, 29 Jan 2011 10:55:57 +0100 Subject: [Python-mode] upcoming release In-Reply-To: <19779.23070.262303.279460@montanaro.dyndns.org> References: <4D433B77.9030602@online.de> <20110128170909.75a5cd8f@python.org> <19779.23070.262303.279460@montanaro.dyndns.org> Message-ID: <4D43E42D.5010603@online.de> Am 29.01.2011 01:06, schrieb skip at pobox.com: > > Barry> I've merged your branch and will play with it over the weekend. > Barry> I'm going to leave it to Skip to verify the XEmacs compatibility > Barry> issues (Skip please let us know if you need help getting > Barry> Andreas's branch). > > I was able to check it out and just load-file'd the python-mode.el. (Should > I have done more?) When I tried to format the triple-quoted in this file: > > """ > triple-quoted string containing "quotation" marks. > triple-quoted string containing "quotation" marks. > triple-quoted string containing "quotation" marks. > triple-quoted string containing "quotation" marks. > triple-quoted string containing "quotation" marks. > """ > > class Foo(object): > @staticmethod > def bar(aList): > for x in aList: > for y in x: > print y > > > It complained about ar-bounds-of-comment-atpt. Shouldn't loading > python-mode.el have complained about that? yes, thanks. Added the require-forms. Trying to load-file the file > where that symbol was defined failed. > > I added the paragraph-fill-warts to the start of load-path and restarted > XEmacs. I then tried to byte-compile python-mode.el. That failed with the > usual (for me) complaint about string-to-syntax being missing. > There was an old version in this branch. Checked in the new one. Also the sequence of new forms had to be changed. Some compile warnings remain with XEmacs 21.5. Could you pull again and check? Andreas > I'll wait for these problems to be resolved before doing more. > > Skip > From andreas.roehler at online.de Sat Jan 29 15:55:43 2011 From: andreas.roehler at online.de (=?UTF-8?B?QW5kcmVhcyBSw7ZobGVy?=) Date: Sat, 29 Jan 2011 15:55:43 +0100 Subject: [Python-mode] upcoming release In-Reply-To: <20110128170909.75a5cd8f@python.org> References: <4D433B77.9030602@online.de> <20110128170909.75a5cd8f@python.org> Message-ID: <4D442A6F.3010106@online.de> Am 28.01.2011 23:09, schrieb Barry Warsaw: > On Jan 28, 2011, at 10:56 PM, Andreas R?hler wrote: > >> enabling XEmacs' handling of triple-quoted-strings fixing bugs known for now >> seems an interesting item from my perspective. paragraph-fill-warts branch >> should enable this. >> https://code.launchpad.net/~a-roehler/python-mode/paragraph-fill-warts It >> comes with a lot of utilities though, some required, some just part of the >> tool-box, where singling-out the required here is possible. I'm hesitating >> to propose that for general release, as people might be scared by the >> material, which is just partly python-related. OTOH, what I'm promessing: it >> pays. These utilities will fasten up editing, python-mode and all other. >> What about to release a thus experimental brunch for XEmacs users first, >> while it will work for all? Andreas > > Andreas, as always, thanks for your hard work on python-mode! It's very much > appreciated. > > I've merged your branch and will play with it over the weekend. Hi Barry, sounds great. I'm going to > leave it to Skip to verify the XEmacs compatibility issues (Skip please let us > know if you need help getting Andreas's branch). > > python-mode.el has always been self-contained, meaning people can easily > download or copy one file and get great Python support in Emacs. Requiring > your utilities changes that, and can make it harder for some folks to adopt > python-mode.el. Indeed, that's my concern too. > I'm not saying that necessarily means it can't be done, but > we do have to think about the ramifications. I'd like to get other folks > thoughts on that. > > OTOH, I encourage you to get your code into upstream Emacs and XEmacs. That > would certainly make our lives easy again. :) > > Do you think it would be possible and easy to pull out just the parts that > python-mode.el needs and include those in that file? That can be done. OTOH it's rather hard keeping that stuff parallel. > If not, then what about > making sure python-mode.el gracefully degrades when those extra files aren't > there? > Don't see that, comment below. > By that I mean, if someone does not have your new utilities, python-mode.el > should at least work as well as it does currently. python-mode.el should then > take advantage of your utilities if they're available. > > Thoughts? > -Barry As it's XEmacs only, which enforced the re-write, maybe we should wait if it works there. In case it works, could extract the needed stuff to it's required minimum. Nontheless GNU Emacs won't need it, so keeping the syntax-parsing as it is for GNU Emacs users will be an option. Also in case XEmacs merges up to GNU code, the regexp-backed parser will not be needed any more. OTOH there are some gains adressed already in the second-level-command blueprint. For me the best would be maintaining for a certain time basically three branches - the classic, presently de facto GNU only - XEmacs special triple quoted string debugged, but fine for GNU Emacs also - a second-level-command enabled IDE. As this slc's will count in thousands and ten-thousands, using it needs an understandings of it's construction, i.e. of the cross-use of it's underlying lists: `ar-hide-bracketed-in-line-atpt' for example hides everything insides brackets within the given line. Resp. `ar-show-bracketed-in-line-atpt' displays it again, `ar-hide-show-bracketed-in-line-atpt' toggles this state. You have `ar-hide-bracketed-in-parentized-atpt' and so on. See the comment in `thingatpt-utils-base.el' for more. As for the latter, think we still need some time to discuss and check it's usefulness. Andreas -- https://code.launchpad.net/~a-roehler/python-mode/python-mode-components https://code.launchpad.net/s-x-emacs-werkstatt/ From skip at pobox.com Sat Jan 29 16:03:54 2011 From: skip at pobox.com (skip at pobox.com) Date: Sat, 29 Jan 2011 09:03:54 -0600 Subject: [Python-mode] upcoming release In-Reply-To: <4D43E42D.5010603@online.de> References: <4D433B77.9030602@online.de> <20110128170909.75a5cd8f@python.org> <19779.23070.262303.279460@montanaro.dyndns.org> <4D43E42D.5010603@online.de> Message-ID: <19780.11354.58382.969185@montanaro.dyndns.org> Andreas> Could you pull again and check? I get failures when I visit a .py file. load-path includes your version at the front: ("/Users/skip/src/paragraph-fill-warts" "/Users/skip/emacs/sql" "/Users/skip/emacs/url" "/Users/skip/emacs" "/Users/skip/local/lib/xemacs/site-lisp" ... "/Users/skip/local/lib/xemacs-21.4.22/lisp/") and (find-library "python-mode") confirms that it finds your version. When I visit a .py file I get this error though: File mode specification error: (file-error "Cannot open load file: %s" misc-utils) Skip From andreas.roehler at online.de Sat Jan 29 16:18:52 2011 From: andreas.roehler at online.de (=?ISO-8859-1?Q?Andreas_R=F6hler?=) Date: Sat, 29 Jan 2011 16:18:52 +0100 Subject: [Python-mode] upcoming release In-Reply-To: <19780.11354.58382.969185@montanaro.dyndns.org> References: <4D433B77.9030602@online.de> <20110128170909.75a5cd8f@python.org> <19779.23070.262303.279460@montanaro.dyndns.org> <4D43E42D.5010603@online.de> <19780.11354.58382.969185@montanaro.dyndns.org> Message-ID: <4D442FDC.3020308@online.de> Am 29.01.2011 16:03, schrieb skip at pobox.com: > > Andreas> Could you pull again and check? > > I get failures when I visit a .py file. load-path includes your version at > the front: > > ("/Users/skip/src/paragraph-fill-warts" "/Users/skip/emacs/sql" > "/Users/skip/emacs/url" "/Users/skip/emacs" > "/Users/skip/local/lib/xemacs/site-lisp" > ... > "/Users/skip/local/lib/xemacs-21.4.22/lisp/") > > and (find-library "python-mode") confirms that it finds your version. > > When I visit a .py file I get this error though: > > File mode specification error: (file-error "Cannot open load file: %s" misc-utils) > > Skip > Ok, so let's have it. Pushed just now. Thanks and sorry... BTW, as mentioned in another posting, will strip down all that stuff if it works for you finally. Andreas From skip at pobox.com Sat Jan 29 17:12:01 2011 From: skip at pobox.com (skip at pobox.com) Date: Sat, 29 Jan 2011 10:12:01 -0600 Subject: [Python-mode] upcoming release In-Reply-To: <4D442FDC.3020308@online.de> References: <4D433B77.9030602@online.de> <20110128170909.75a5cd8f@python.org> <19779.23070.262303.279460@montanaro.dyndns.org> <4D43E42D.5010603@online.de> <19780.11354.58382.969185@montanaro.dyndns.org> <4D442FDC.3020308@online.de> Message-ID: <19780.15441.78502.866889@montanaro.dyndns.org> Andreas> Ok, so let's have it. Pushed just now. File mode specification error: (file-error "Cannot open load file: %s" string-strip) load-path: `load-path' is a simple built-in variable. Value: ("/Users/skip/src/paragraph-fill-warts" ... Skip From andreas.roehler at online.de Sat Jan 29 17:26:01 2011 From: andreas.roehler at online.de (=?ISO-8859-1?Q?Andreas_R=F6hler?=) Date: Sat, 29 Jan 2011 17:26:01 +0100 Subject: [Python-mode] upcoming release In-Reply-To: <19780.15441.78502.866889@montanaro.dyndns.org> References: <4D433B77.9030602@online.de> <20110128170909.75a5cd8f@python.org> <19779.23070.262303.279460@montanaro.dyndns.org> <4D43E42D.5010603@online.de> <19780.11354.58382.969185@montanaro.dyndns.org> <4D442FDC.3020308@online.de> <19780.15441.78502.866889@montanaro.dyndns.org> Message-ID: <4D443F99.4040405@online.de> Am 29.01.2011 17:12, schrieb skip at pobox.com: > > Andreas> Ok, so let's have it. Pushed just now. > > File mode specification error: (file-error "Cannot open load file: %s" string-strip) > ehm... pushed > load-path: > > `load-path' is a simple built-in variable. > > Value: ("/Users/skip/src/paragraph-fill-warts" ... > > Skip > From skip at pobox.com Sat Jan 29 17:41:59 2011 From: skip at pobox.com (skip at pobox.com) Date: Sat, 29 Jan 2011 10:41:59 -0600 Subject: [Python-mode] upcoming release In-Reply-To: <4D433B77.9030602@online.de> References: <4D433B77.9030602@online.de> Message-ID: <19780.17239.654328.558565@montanaro.dyndns.org> Latest error: File mode specification error: (file-error "Cannot open load file: %s" sh-beg-end) Skip From andreas.roehler at online.de Sat Jan 29 18:07:22 2011 From: andreas.roehler at online.de (=?ISO-8859-1?Q?Andreas_R=F6hler?=) Date: Sat, 29 Jan 2011 18:07:22 +0100 Subject: [Python-mode] upcoming release In-Reply-To: <19780.17239.654328.558565@montanaro.dyndns.org> References: <4D433B77.9030602@online.de> <19780.17239.654328.558565@montanaro.dyndns.org> Message-ID: <4D44494A.6010809@online.de> Am 29.01.2011 17:41, schrieb skip at pobox.com: > Latest error: > > File mode specification error: (file-error "Cannot open load file: %s" sh-beg-end) Well, it's able to jump to beginnings- and end of shell blocks, what the common GNU mode can't This world should be finite though... added and pushed > > Skip > > From skip at pobox.com Sat Jan 29 18:16:57 2011 From: skip at pobox.com (skip at pobox.com) Date: Sat, 29 Jan 2011 11:16:57 -0600 Subject: [Python-mode] Latest error Message-ID: <19780.19337.223337.875509@montanaro.dyndns.org> Looks like thingatpt-utils-base requires thingatpt-highlight which doesn't exist in the checkout. I evaled all the (require) statements from the .el files in a (progn) block: (progn (require 'easymenu) (require 'ansi-color) (require 'ar-comment-lor) (require 'beg-end) (require 'cl) (require 'comint) (require 'compile) (require 'custom) (require 'info-look) (require 'misc-utils) (require 'mmm-auto) (require 'pymacs) (require 'reporter) (require 'sh-beg-end) (require 'sh-script) (require 'string-strip) (require 'thingatpt-utils-base) (require 'overlay) (require 'imenu) (require 'thing-at-point-utils) (require 'thingatpt-highlight) (require 'python-mode) ) thingatpt-highlight was the only one it complained about. Skip From andreas.roehler at online.de Sat Jan 29 18:31:02 2011 From: andreas.roehler at online.de (=?ISO-8859-1?Q?Andreas_R=F6hler?=) Date: Sat, 29 Jan 2011 18:31:02 +0100 Subject: [Python-mode] Latest error In-Reply-To: <19780.19337.223337.875509@montanaro.dyndns.org> References: <19780.19337.223337.875509@montanaro.dyndns.org> Message-ID: <4D444ED6.5050605@online.de> Am 29.01.2011 18:16, schrieb skip at pobox.com: > > Looks like thingatpt-utils-base requires thingatpt-highlight which doesn't > exist in the checkout. I evaled all the (require) statements from the .el > files in a (progn) block: > > (progn > (require 'easymenu) > (require 'ansi-color) > (require 'ar-comment-lor) > (require 'beg-end) > (require 'cl) > (require 'comint) > (require 'compile) > (require 'custom) > (require 'info-look) > (require 'misc-utils) > (require 'mmm-auto) > (require 'pymacs) > (require 'reporter) > (require 'sh-beg-end) > (require 'sh-script) > (require 'string-strip) > (require 'thingatpt-utils-base) > (require 'overlay) > (require 'imenu) > (require 'thing-at-point-utils) > (require 'thingatpt-highlight) > (require 'python-mode) > ) > > thingatpt-highlight was the only one it complained about. > > Skip Hmm, seems I underestimated the issue. added and pushed. Thanks being that attentive. From skip at pobox.com Sat Jan 29 18:52:16 2011 From: skip at pobox.com (skip at pobox.com) Date: Sat, 29 Jan 2011 11:52:16 -0600 Subject: [Python-mode] Latest error In-Reply-To: <4D444ED6.5050605@online.de> References: <19780.19337.223337.875509@montanaro.dyndns.org> <4D444ED6.5050605@online.de> Message-ID: <19780.21456.805836.515307@montanaro.dyndns.org> >> thingatpt-highlight was the only one it complained about. Andreas> Hmm, seems I underestimated the issue. Andreas> added and pushed. I'm getting farther. Looks like thingatpt-highlight was missing (when (featurep 'xemacs) (require 'overlay)) so I added that to get the make-overlay function. Then I could visit the Python file without errors. Recall the file looks like this (without the extra indentation): """ triple-quoted string containing "quotation" marks. triple-quoted string containing "quotation" marks. triple-quoted string containing "quotation" marks. triple-quoted string containing "quotation" marks. triple-quoted string containing "quotation" marks. """ class Foo(object): @staticmethod def bar(aList): for x in aList: for y in x: print y When I try to fill the docstring using fill-paragraph-or-region (M-q) with point ahead of the first 't', it still deletes the space ahead of the first single quotation mark, leaving me with this: """ triple-quoted string containing"quotation" marks. triple-quoted string containing "quotation" marks. triple-quoted string containing "quotation" marks. triple-quoted string containing "quotation" marks. triple-quoted string containing "quotation" marks. """ If I place point at the beginning of the last line and fill, I get this: """ triple-quoted string containing"quotation" marks. triple-quoted string containing "quotation" marks. triple-quoted string containing "quotation" marks. triple-quoted string containing "quotation" marks. triple-quoted string containing"quotation" marks. """ Repeat again, and I get: """ triple-quoted string containing"quotation" marks. triple-quoted string containing "quotation" marks. triple-quoted string containing "quotation" marks. triple-quoted string containing"quotation" marks. triple-quoted string containing"quotation" marks. """ I can proceed to do this until I'm left with a single line in the docstring. Skip From andreas.roehler at online.de Sat Jan 29 19:42:50 2011 From: andreas.roehler at online.de (=?ISO-8859-1?Q?Andreas_R=F6hler?=) Date: Sat, 29 Jan 2011 19:42:50 +0100 Subject: [Python-mode] Latest error In-Reply-To: <19780.21456.805836.515307@montanaro.dyndns.org> References: <19780.19337.223337.875509@montanaro.dyndns.org> <4D444ED6.5050605@online.de> <19780.21456.805836.515307@montanaro.dyndns.org> Message-ID: <4D445FAA.5090909@online.de> Am 29.01.2011 18:52, schrieb skip at pobox.com: > >> thingatpt-highlight was the only one it complained about. > > Andreas> Hmm, seems I underestimated the issue. > > Andreas> added and pushed. > > I'm getting farther. Looks like thingatpt-highlight was missing > > (when (featurep 'xemacs) (require 'overlay)) > > so I added that to get the make-overlay function. Then I could visit the > Python file without errors. Recall the file looks like this (without the > extra indentation): > > """ > triple-quoted string containing "quotation" marks. > triple-quoted string containing "quotation" marks. > triple-quoted string containing "quotation" marks. > triple-quoted string containing "quotation" marks. > triple-quoted string containing "quotation" marks. > """ > > class Foo(object): > @staticmethod > def bar(aList): > for x in aList: > for y in x: > print y > > When I try to fill the docstring using fill-paragraph-or-region (M-q) with > point ahead of the first 't', it still deletes the space ahead of the first > single quotation mark, leaving me with this: > > """ > triple-quoted string containing"quotation" marks. which is the charateristic error of failing forward-sexp, As that form doesn't exist in new version, it means, we got the old chunk back See the error was done with revision 391 Will take some minutes to get it back. > triple-quoted string containing "quotation" marks. > triple-quoted string containing "quotation" marks. > triple-quoted string containing "quotation" marks. > triple-quoted string containing "quotation" marks. > """ > > If I place point at the beginning of the last line and fill, I get this: > > """ > triple-quoted string containing"quotation" marks. > triple-quoted string containing "quotation" marks. > triple-quoted string containing "quotation" marks. > triple-quoted string containing "quotation" marks. triple-quoted string containing"quotation" marks. > """ > > Repeat again, and I get: > > """ > triple-quoted string containing"quotation" marks. > triple-quoted string containing "quotation" marks. > triple-quoted string containing "quotation" marks. triple-quoted string containing"quotation" marks. triple-quoted string containing"quotation" marks. > """ > > I can proceed to do this until I'm left with a single line in the docstring. > > Skip > From andreas.roehler at online.de Sat Jan 29 22:15:25 2011 From: andreas.roehler at online.de (=?ISO-8859-15?Q?Andreas_R=F6hler?=) Date: Sat, 29 Jan 2011 22:15:25 +0100 Subject: [Python-mode] paragraph-fill-warts branch Message-ID: <4D44836D.8050603@online.de> Hi Skip, the old bug should be gone now. As its redone from the bottom, filling isn't correct yet. However, borders of triple-quoted-string now are recognised, `ar-bounds-of-triplequoted-atpt' should report it for example, the remaining should not be a rocky mountain. Andreas From skip at pobox.com Sat Jan 29 22:20:56 2011 From: skip at pobox.com (skip at pobox.com) Date: Sat, 29 Jan 2011 15:20:56 -0600 Subject: [Python-mode] paragraph-fill-warts branch In-Reply-To: <4D44836D.8050603@online.de> References: <4D44836D.8050603@online.de> Message-ID: <19780.33976.592485.533735@montanaro.dyndns.org> Andreas> the old bug should be gone now. Andreas> As its redone from the bottom, filling isn't correct yet. Andreas> However, borders of triple-quoted-string now are recognised, Andreas> `ar-bounds-of-triplequoted-atpt' should report it for example, Andreas> the remaining should not be a rocky mountain. Looks much better. Goes from this: """ triple-quoted string containing "quotation" marks. triple-quoted string containing "quotation" marks. triple-quoted string containing "quotation" marks. triple-quoted string containing "quotation" marks. triple-quoted string containing "quotation" marks. """ to this: """ triple-quoted string containing "quotation" marks. triple-quoted string containing "quotation" marks. triple-quoted string containing "quotation" marks. triple-quoted string containing "quotation" marks. triple-quoted string containing "quotation" marks. """ no matter where I place the cursor. Thanks, Skip From andreas.roehler at online.de Sun Jan 30 21:16:30 2011 From: andreas.roehler at online.de (=?UTF-8?B?QW5kcmVhcyBSw7ZobGVy?=) Date: Sun, 30 Jan 2011 21:16:30 +0100 Subject: [Python-mode] paragraph-fill-warts branch In-Reply-To: <20110129213429.218940@gmx.net> References: <4D44836D.8050603@online.de> <19780.33976.592485.533735@montanaro.dyndns.org> <20110129213429.218940@gmx.net> Message-ID: <4D45C71E.9020407@online.de> Am 29.01.2011 22:34, schrieb g.brandl at gmx.net: > > -------- Original-Nachricht -------- >> Datum: Sat, 29 Jan 2011 15:20:56 -0600 >> Von: skip at pobox.com >> An: "Andreas R?hler" >> CC: python-mode at python.org >> Betreff: Re: [Python-mode] paragraph-fill-warts branch > >> >> Andreas> the old bug should be gone now. >> >> Andreas> As its redone from the bottom, filling isn't correct yet. >> >> Andreas> However, borders of triple-quoted-string now are recognised, >> >> Andreas> `ar-bounds-of-triplequoted-atpt' should report it for >> example, >> >> Andreas> the remaining should not be a rocky mountain. >> >> Looks much better. Goes from this: >> >> """ >> triple-quoted string containing "quotation" marks. >> triple-quoted string containing "quotation" marks. >> triple-quoted string containing "quotation" marks. >> triple-quoted string containing "quotation" marks. >> triple-quoted string containing "quotation" marks. >> """ >> >> to this: >> >> """ triple-quoted string containing "quotation" marks. triple-quoted >> string >> containing "quotation" marks. triple-quoted string containing >> "quotation" >> marks. triple-quoted string containing "quotation" marks. >> triple-quoted >> string containing "quotation" marks. """ >> >> no matter where I place the cursor. > > Which is not how this should work. > > * If there is an initial linebreak it should remain there. > * If there is a final linebreak it should remain there. > > And if there is no initial linebreak, please do not put a > space between the quotes and the docstring text. > > Georg Hi Georg, hi Skip, just checked in a new version of fill-warts branch and also components branch It's definitly upwards the hill, but some issues remain. We have a bug in GNU's fill.el After paragraph-fill-function is called, it should retire from all other work. Unfortunatly later on (fill-region-as-paragraph beg end justify) comes across and messes it up. Altogether looks with GNU still better than with XEmacs, which progresses also. To make some pieces from the remaining: Could you check with `py-fill-paragraph' directly leaving out M-q? That would make it easier coming to some result. When reporting the remaining bugs, please make an entry in the tracker and mention the kind of Emacs/version. Thanks all Andreas From g.brandl at gmx.net Sat Jan 29 22:34:29 2011 From: g.brandl at gmx.net (g.brandl at gmx.net) Date: Sat, 29 Jan 2011 22:34:29 +0100 Subject: [Python-mode] paragraph-fill-warts branch In-Reply-To: <19780.33976.592485.533735@montanaro.dyndns.org> References: <4D44836D.8050603@online.de> <19780.33976.592485.533735@montanaro.dyndns.org> Message-ID: <20110129213429.218940@gmx.net> -------- Original-Nachricht -------- > Datum: Sat, 29 Jan 2011 15:20:56 -0600 > Von: skip at pobox.com > An: "Andreas R?hler" > CC: python-mode at python.org > Betreff: Re: [Python-mode] paragraph-fill-warts branch > > Andreas> the old bug should be gone now. > > Andreas> As its redone from the bottom, filling isn't correct yet. > > Andreas> However, borders of triple-quoted-string now are recognised, > > Andreas> `ar-bounds-of-triplequoted-atpt' should report it for > example, > > Andreas> the remaining should not be a rocky mountain. > > Looks much better. Goes from this: > > """ > triple-quoted string containing "quotation" marks. > triple-quoted string containing "quotation" marks. > triple-quoted string containing "quotation" marks. > triple-quoted string containing "quotation" marks. > triple-quoted string containing "quotation" marks. > """ > > to this: > > """ triple-quoted string containing "quotation" marks. triple-quoted > string > containing "quotation" marks. triple-quoted string containing > "quotation" > marks. triple-quoted string containing "quotation" marks. > triple-quoted > string containing "quotation" marks. """ > > no matter where I place the cursor. Which is not how this should work. * If there is an initial linebreak it should remain there. * If there is a final linebreak it should remain there. And if there is no initial linebreak, please do not put a space between the quotes and the docstring text. Georg -- NEU: FreePhone - kostenlos mobil telefonieren und surfen! Jetzt informieren: http://www.gmx.net/de/go/freephone From skip at pobox.com Sun Jan 30 23:16:40 2011 From: skip at pobox.com (skip at pobox.com) Date: Sun, 30 Jan 2011 16:16:40 -0600 Subject: [Python-mode] paragraph-fill-warts branch In-Reply-To: <4D45C71E.9020407@online.de> References: <4D44836D.8050603@online.de> <19780.33976.592485.533735@montanaro.dyndns.org> <20110129213429.218940@gmx.net> <4D45C71E.9020407@online.de> Message-ID: <19781.58184.334425.553587@montanaro.dyndns.org> Andreas> When reporting the remaining bugs, please make an entry in the Andreas> tracker and mention the kind of Emacs/version. Done: https://bugs.launchpad.net/python-mode/+bug/710373 Andreas, if you would like a login on my Mac laptop so you can play with my version of XEmacs, let me know. I suspect you will converge on working code more quickly if you don't have to wait for me to complain. Skip From andreas.roehler at online.de Mon Jan 31 07:45:06 2011 From: andreas.roehler at online.de (=?ISO-8859-1?Q?Andreas_R=F6hler?=) Date: Mon, 31 Jan 2011 07:45:06 +0100 Subject: [Python-mode] paragraph-fill-warts branch In-Reply-To: <19781.58184.334425.553587@montanaro.dyndns.org> References: <4D44836D.8050603@online.de> <19780.33976.592485.533735@montanaro.dyndns.org> <20110129213429.218940@gmx.net> <4D45C71E.9020407@online.de> <19781.58184.334425.553587@montanaro.dyndns.org> Message-ID: <4D465A72.3020104@online.de> Am 30.01.2011 23:16, schrieb skip at pobox.com: > > Andreas> When reporting the remaining bugs, please make an entry in the > Andreas> tracker and mention the kind of Emacs/version. > > Done: > > https://bugs.launchpad.net/python-mode/+bug/710373 > > Andreas, if you would like a login on my Mac laptop so you can play with my > version of XEmacs, let me know. I suspect you will converge on working code > more quickly if you don't have to wait for me to complain. > > Skip > Thanks, looks like a nice play. So I must log in via ssh? May you use my public key vom lp? Not sure about the steps for this. Andreas