On Feb 1, 2008, at 9:32 AM, Alexander Limi wrote:
You probably see where I'm going with this, but: I'd like to ship
3.1 with a set of .po files that do not contain the strings from
Plone 2.5. Hanno said it would take him a couple of hours to weed
out the stuff that is 2.5-specific, and
On Feb 1, 2008, at 12:04 PM, Martijn Pieters wrote:
On Feb 1, 2008 11:51 AM, Andreas Zeidler [EMAIL PROTECTED] wrote:
talking about weeding out stuff bring another thing to mind. not
exactly related to translations, but i'll throw it in here anyway:
tools like pylint[1] and pyflakes[2] have
On Feb 1, 2008, at 11:51 AM, Andreas Zeidler wrote:
[3] which basically means all packages except `statusmessages`
(guess who owns that ;)) as you can see from the attached list
counting the warnings; i should note that this list still contains
warnings about namespace package
On 01.02.2008, at 12:07, Andreas Zeidler wrote:
On Feb 1, 2008, at 12:04 PM, Martijn Pieters wrote:
On Feb 1, 2008 11:51 AM, Andreas Zeidler [EMAIL PROTECTED] wrote:
talking about weeding out stuff bring another thing to mind. not
exactly related to translations, but i'll throw it in here
On Feb 1, 2008, at 1:02 PM, Tom Lazar wrote:
On 01.02.2008, at 12:07, Andreas Zeidler wrote:
yes, i'm very much aware of these problems having used pyflakes
myself for quite some time now. that's one of the reasons i'm
bringing this up here (instead of starting to weed away on
trunk :)).
On Feb 1, 2008, at 7:00 PM, Martijn Pieters wrote:
On 1. feb.. 2008, at 12.28, Martin Aspeli wrote:
Careful with weeding imports. I recently had to fix a migration
issue
for a customer, where a persistent tool had been moved into another
module with an import at the old location. Someone else
