Using a Callback Function - ftplib

seldan24 seldan24 at
Tue Aug 18 19:18:42 CEST 2009

On Aug 18, 6:02 am, Nitebirdz <nitebi... at> wrote:
> On Mon, Aug 17, 2009 at 11:10:25AM -0700, seldan24 wrote:
> > I didn't even notice the higher level methods.  I changed the
> > retrieval line to:
> > ftp.nlst("testfile*.txt")
> > This works great.  The result is even captured in an array.  I really
> > have no idea what the difference between a LIST and NLST is within
> > FTP.  Never delved that deep into it.  I did notice that an NLST will
> > return a specific FTP code if a file doesn't exist, whereas a LIST
> > doesn't.  So, I ended up using NLST as that'll generate an
> > ftplib.error_perm exception.  Based on if the job cares if a file is
> > not available or not (some do, some don't), I'll either exit, or
> > continue on with the file loop.
> The following thread from a NetBSD mailing list may help clarify this
> issue:
> NLST returns a machine-readable list of names, while LIST returns a
> human-readable list.  Hene the presence of the FTP code in the case of
> NLST.  


Thanks for the information.  I knew it stood for 'named list' but had
no idea how that differed from the standard.  I appreciate the link.

More information about the Python-list mailing list