× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



On Wed, Jun 28, 2017 at 4:48 PM, John Yeung <gallium.arsenide@xxxxxxxxx>
wrote:

On Wed, Jun 28, 2017 at 6:00 PM, Charles Wilt <charles.wilt@xxxxxxxxx>
wrote:
I used wireshark to capture the FTP session and I can see the code being
sent out incorrectly from my PC.

What does this mean? In what way is the code sent out incorrectly, and
how *should* the code be sent out? I don't even know which "code"
we're talking about. And in any case, it's hard for me to imagine how
this would result in *lines* that show up in the wrong order. Second
half of file (that is, source member) missing, sure. Everything
garbled, yes, we've all seen that. But *lines* in the wrong order?
That just boggles the mind.


​Code as in the source code...

Incorrectly as in the first packet contains the 1st line from the source
file; and only the first line.

The second packet packet starts with source line #17 and contains #17, #18,
??, and #2.

The ?? is because I'm not sure what line it is, as it's a separator line
with all asterisks. ​



So the issue appears to be in python.

Apparently. But you implied it had been working fine before?


​Yep.




I'm not a python guru...but the script uses ftplib...which seems to be a
standard python library.

That is indeed part of the standard library. It should be very robust.
What version of Python are you using? Would it be possible to share
the script?



​Python 2.7.12

And that hasn't changed either...​

Charles

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.