Opened 10 years ago

Last modified 6 years ago

#626 enhancement new

Split tutorial finger code into libraries

Reported by: hypatia Owned by: kehander1
Priority: low Milestone:
Component: core Keywords: documentation
Cc: thijs, kehander1 Branch:
Author: Launchpad Bug:

Description


Attachments (1)

finger19-lib.tar.gz (1.2 KB) - added by kehander1 6 years ago.
finger19.tac libraries

Download all attachments as: .zip

Change History (8)

comment:1 Changed 10 years ago by hypatia

I may change my mind about this one, but after editing the tutorial code last
night, and having to push my changes into three different files, I think it
might be better to have the application split into more than one file after a
certain point.

May well make it easier for readers to see what's being added at each point too,
as well as making the pages smaller again by *linking* to the already seen .py
files rather than including them in the HTML output, and only displaying .py
files containing new code at each step.

comment:2 Changed 8 years ago by hypatia

  • Component set to core
  • Owner changed from hypatia to edsuom

comment:3 Changed 8 years ago by hypatia

  • Cc hypatia removed

comment:4 Changed 6 years ago by thijs

  • Cc thijs added

comment:5 Changed 6 years ago by thijs

  • Cc kehander1 added

Changed 6 years ago by kehander1

finger19.tac libraries

comment:6 Changed 6 years ago by kehander1

  • Keywords review added
  • Owner edsuom deleted

Something like this, then?

These are derived from the files in branch 25111. ( #532 )

comment:7 Changed 6 years ago by exarkun

  • Keywords review removed
  • Owner set to kehander1

Good start. These files need to be actual Python source files though so that they can be imported from the rest of the listings, and the rest of the listings need to be updated to import them instead of re-defining what they contain. I also don't think it's a good idea to base these changes off of the #532 branch, unless you want to wait for #532 to be finished before doing any more work on this. If these changes are based on the #532 branch, then there's no way to apply them until #532 is resolved. Doing this refactoring first based on trunk might also make #532 easier to resolve.

Note: See TracTickets for help on using tickets.