This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author ajvant
Recipients StevenJ, ajvant, chasonr, christian.heimes, giampaolo.rodola, janssen, jelie, pitrou
Date 2010-11-06.18:22:30
SpamBayes Score 1.6402601e-11
Marked as misclassified No
Message-id <4CD59CF4.16302.1E502F87@ajvant.gmail.com>
In-reply-to <1289064186.46.0.691566209426.issue1926@psf.upfronthosting.co.za>
Content
On 6 Nov 2010 at 17:23, StevenJ wrote:

> As it stands, the nntplib can cause the cached capabilities to be
> refreshed at certain points automatically (as it should), but I think
> it should be possible for the caller of the method to also specify
> that fresh capabilities are required and not cached ones.

I agree. I actually added a way to do this when I functioned out 
__init__, so that starttls could refresh it when required. 

It was ugly and not exposed to the caller though. 

> something like this perhaps? :
> 
> mynntp.getcapabilites(refresh=True)

My method sucked, this one doesn't. Might belong in a separate issue 
though. (I feel like a bit of a hypocrite saying that now) 

--

Andrew
History
Date User Action Args
2010-11-06 18:22:31ajvantsetrecipients: + ajvant, janssen, pitrou, giampaolo.rodola, christian.heimes, chasonr, jelie, StevenJ
2010-11-06 18:22:30ajvantlinkissue1926 messages
2010-11-06 18:22:30ajvantcreate