[BioPython] The count method of a Seq (or MutableSeq) object

[Leighton Pritchard]

In the spirit of being blindingly obvious, how about:

Seq.overlapping_count()

;)

L.


On 06/03/2009 11:52, "Michiel de Hoon" <mjldehoon at yahoo.com> wrote:

> 
>>> Another option is to continue to use count() for a Python-style count,
>>> and to add a new method that does a overlapping-type count. For this
>>> new method we'd need a clear but short name, and I can't think of
>>> anything now.
>>> 
>> Did you like plan (c), which preserves the Python string style count
>> as the default but offers the non-overlapping count via an optional
>> argument?
>> 
> It's also OK, but if we use a different method name we can leave count()
> untouched altogether.

-- 
Dr Leighton Pritchard MRSC
D131, Plant Pathology Programme, SCRI
Errol Road, Invergowrie, Perth and Kinross, Scotland, DD2 5DA
e:lpritc at scri.ac.uk       w:http://www.scri.ac.uk/staff/leightonpritchard
gpg/pgp: 0xFEFC205C       tel:+44(0)1382 562731 x2405


______________________________________________________________________
SCRI, Invergowrie, Dundee, DD2 5DA.  
The Scottish Crop Research Institute is a charitable company limited by
guarantee. 
Registered in Scotland No: SC 29367.
Recognised by the Inland Revenue as a Scottish Charity No: SC 006662.


DISCLAIMER:

This email is from the Scottish Crop Research Institute, but the views 
expressed by the sender are not necessarily the views of SCRI and its 
subsidiaries.  This email and any files transmitted with it are
confidential

to the intended recipient at the e-mail address to which it has been 
addressed.  It may not be disclosed or used by any other than that
addressee.
If you are not the intended recipient you are requested to preserve this

confidentiality and you must not use, disclose, copy, print or rely on
this 
e-mail in any way. Please notify postmaster at scri.ac.uk quoting the 
name of the sender and delete the email from your system.

Although SCRI has taken reasonable precautions to ensure no viruses are 
present in this email, neither the Institute nor the sender accepts any 
responsibility for any viruses, and it is your responsibility to scan
the email and the attachments (if any).
______________________________________________________________________