handful of tidy-up patches from 1.7.1 cycle #1131

Closed
opened 2010-07-20 04:27:30 +00:00 by zooko · 9 comments
zooko commented 2010-07-20 04:27:30 +00:00
Owner

I have three patches here which I chose to keep out of trunk during 1.7.1.

Please review!

I have three patches here which I chose to keep out of trunk during 1.7.1. Please review!
tahoe-lafs added the
code
minor
enhancement
1.7.0
labels 2010-07-20 04:27:30 +00:00
tahoe-lafs added this to the 1.8β milestone 2010-07-20 04:27:30 +00:00
zooko commented 2010-07-20 04:27:50 +00:00
Author
Owner

Attachment three_cleanups.dpatch.txt (16171 bytes) added

**Attachment** three_cleanups.dpatch.txt (16171 bytes) added
davidsarah commented 2010-07-20 05:25:51 +00:00
Author
Owner

Please wrap the lines longer than about 100 chars.

Also, random_unicode seems more general than it needs to be. (It would probably be slightly simpler to choose random unicode code points, rather than to choose a random UTF-8 encoding for each character and loop until it is valid, since the encoded length doesn't appear to be critical.)

Otherwise looks fine. Please keep this ticket open so I can attach my own cleanup patches :-)

Please wrap the lines longer than about 100 chars. Also, `random_unicode` seems more general than it needs to be. (It would probably be slightly simpler to choose random unicode code points, rather than to choose a random UTF-8 encoding for each character and loop until it is valid, since the encoded length doesn't appear to be critical.) Otherwise looks fine. Please keep this ticket open so I can attach my own cleanup patches :-)
zooko commented 2010-07-21 16:51:23 +00:00
Author
Owner

Replying to davidsarah:

Please wrap the lines longer than about 100 chars.

Okay (grumble).

Also, random_unicode seems more general than it needs to be. (It would probably be slightly simpler to choose random unicode code points,

Yeah, for the purposes of this benchmark, it could even just be a random ascii string or something. How would one choose random unicode code points other than the way random_unicode() does it?

Replying to [davidsarah](/tahoe-lafs/trac-2024-07-25/issues/1131#issuecomment-120464): > Please wrap the lines longer than about 100 chars. Okay (*grumble*). > Also, `random_unicode` seems more general than it needs to be. (It would probably be slightly simpler to choose random unicode code points, Yeah, for the purposes of this benchmark, it could even just be a random ascii string or something. How would one choose random unicode code points other than the way `random_unicode()` does it?
zooko commented 2010-07-23 05:34:10 +00:00
Author
Owner

Removing review-needed. I'll line-wrap, probably leave the silly random_unicode() as is, and commit the patch. Leaving this ticket open for other post-1.7.1 cleanup patches. :-)

Removing review-needed. I'll line-wrap, probably leave the silly `random_unicode()` as is, and commit the patch. Leaving this ticket open for other post-1.7.1 cleanup patches. :-)
davidsarah commented 2010-08-02 04:37:54 +00:00
Author
Owner

There's an uncommented print statement in is_happy_enough. Otherwise fine.

There's an uncommented print statement in `is_happy_enough`. Otherwise fine.
zooko commented 2010-08-02 06:46:16 +00:00
Author
Owner

Below is a patch to reformat lines to < 100 chars and to tidy up logging in immutable/upload.py.

Below is a patch to reformat lines to < 100 chars and to tidy up logging in immutable/upload.py.
zooko commented 2010-08-02 06:46:48 +00:00
Author
Owner

Attachment tidy-up-logging.dpatch.txt (24549 bytes) added

**Attachment** tidy-up-logging.dpatch.txt (24549 bytes) added
davidsarah commented 2010-08-03 18:33:01 +00:00
Author
Owner

Applied for 1.8beta in [4632/ticket798], [4634/ticket798], [4637/ticket798]. Uncommented print statement removed in [4636/ticket798].

Applied for 1.8beta in [4632/ticket798], [4634/ticket798], [4637/ticket798]. Uncommented print statement removed in [4636/ticket798].
tahoe-lafs added the
fixed
label 2010-08-03 18:33:01 +00:00
davidsarah closed this issue 2010-08-03 18:33:01 +00:00
davidsarah commented 2010-08-03 18:34:14 +00:00
Author
Owner

... and [4633/ticket798].

... and [4633/ticket798].
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: tahoe-lafs/trac-2024-07-25#1131
No description provided.