[Bugs] #2093 UNSP: tamyblock not loaded

Sugar Labs Bugs bugtracker-noreply at sugarlabs.org
Tue Sep 21 16:01:44 EDT 2010


#2093: tamyblock not loaded
------------------------------------------+---------------------------------
    Reporter:  walter                     |          Owner:  kandarpk                   
        Type:  defect                     |         Status:  assigned                   
    Priority:  Unspecified by Maintainer  |      Milestone:  Unspecified by Release Team
   Component:  Turtleart                  |        Version:  Unspecified                
    Severity:  Unspecified                |       Keywords:  sugar-love                 
Distribution:  Unspecified                |   Status_field:  Unconfirmed                
------------------------------------------+---------------------------------

Comment(by walter):

 A bit more detail:

 tamyblock.py is a collection of sample Python code for use with the Import
 Python block within Turtle Blocks (the block with the Python icon on the
 red Extras palette). This block will import files with mime-type python
 and execute that code when the block is run as part of a Turtle Art
 program.

 When Turtle Blocks is first launched, a copy of tamyblock.py, which is
 included in the .xo bundle, is copied into the Journal so that it is
 available to browse and modify with the Pippy program and to load into
 Turtle Blocks. Every time there is a new version of Turtle Blocks
 installed, a fresh copy of tamyblocks.py is copied to the Journal.

 The two defects mentioned in this ticket are: (1) apparently sometimes the
 file is not copied into the Journal, resulting in no copy; and (2) the
 file is copied even when there is an unmodified copy already in the
 Journal, resulting in redundant copies.

 Without any log files, it will be hard to resolve #1, unless there is some
 obvious mistake in the logic of the code (See lines 928-968 in
 TurtleArtActivity.py). In regard to #2, it would be reasonable to generate
 a hash from the new file, search the journal for the old file, generate
 another hash, and compare them. If the hash is the same, don't copy the
 file.

-- 
Ticket URL: <http://bugs.sugarlabs.org/ticket/2093#comment:2>
Sugar Labs <http://sugarlabs.org/>
Sugar Labs bug tracking system


More information about the Bugs mailing list