Message 85645 - Python tracker

➜

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	loafman
Recipients	ajaksu2, giampaolo.rodola, loafman
Date	2009-04-06.13:37:13
SpamBayes Score	0.0010409891
Marked as misclassified	No
Message-id	<1239025035.33.0.317027369788.issue1726451@psf.upfronthosting.co.za>
In-reply-to

Content
Clearly not valid if you are strictly RFC compliant, however, if you want to be functional in the real world then it needs to be addressed. ProFTPd is not the only server that handles things this way, so from a functionality and compatibility standpoint, it should be fixed. BTW, I've already voted for functionality over forced compliance by moving duplicity backup from ftplib to ncftp since ncftp talks to most servers without complaint. RFC compliance is nice, but FTP servers just are not compliant in the real world.

Clearly not valid if you are strictly RFC compliant, however, if you
want to be functional in the real world then it needs to be addressed. 
ProFTPd is not the only server that handles things this way, so from a
functionality and compatibility standpoint, it should be fixed.

BTW, I've already voted for functionality over forced compliance by
moving duplicity backup from ftplib to ncftp since ncftp talks to most
servers without complaint.  RFC compliance is nice, but FTP servers just
are not compliant in the real world.

History
Date	User	Action	Args
2009-04-06 13:37:15	loafman	set	recipients: + loafman, giampaolo.rodola, ajaksu2
2009-04-06 13:37:15	loafman	set	messageid: <1239025035.33.0.317027369788.issue1726451@psf.upfronthosting.co.za>
2009-04-06 13:37:14	loafman	link	issue1726451 messages
2009-04-06 13:37:13	loafman	create