Path: csiph.com!fu-berlin.de!uni-berlin.de!not-for-mail From: Dennis Lee Bieber Newsgroups: comp.lang.python Subject: Re: How do you guys tackle a package with poorish documentation? Date: Wed, 13 Jul 2016 00:49:04 -0400 Organization: IISS Elusive Unicorn Lines: 29 Message-ID: References: <3lhbob1monp1ek1rvd3guies9tae7qas8d@4ax.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Trace: news.uni-berlin.de G+JZTVNngHC2+1MMAfDrWQbnokt+ddWcOmYc8/w6/NAw== Return-Path: X-Original-To: python-list@python.org Delivered-To: python-list@mail.python.org X-Spam-Status: OK 0.022 X-Spam-Evidence: '*H*': 0.96; '*S*': 0.00; 'subject:How': 0.09; 'message-id:@4ax.com': 0.09; 'received:80.91': 0.09; 'received:80.91.229': 0.09; 'received:gmane.org': 0.09; 'received:list': 0.09; 'python': 0.10; 'file,': 0.15; '2016': 0.16; 'code?': 0.16; 'data)': 0.16; 'numbered': 0.16; 'received:80.91.229.3': 0.16; 'received:io': 0.16; 'received:plane.gmane.org': 0.16; 'received:psf.io': 0.16; 'sqlite3': 0.16; 'url:home': 0.18; 'load': 0.20; 'matching': 0.23; 'xml': 0.24; 'header:X-Complaints-To:1': 0.26; 'external': 0.27; 'separate': 0.27; 'switch': 0.27; 'question': 0.27; 'subject:skip:d 10': 0.27; 'device': 0.28; '(my': 0.29; 'excel': 0.29; 'books': 0.30; 'normally': 0.30; "i'd": 0.31; 'post': 0.31; 'computing': 0.32; 'run': 0.33; 'source': 0.33; 'extract': 0.33; 'me?': 0.34; 'tue,': 0.34; 'this?': 0.34; 'filter': 0.35; 'formats': 0.35; 'quite': 0.35; 'but': 0.36; 'needed': 0.36; 'there': 0.36; 'to:addr:python-list': 0.36; 'subject:?': 0.36; 'subject:: ': 0.37; 'two': 0.37; 'received:org': 0.37; 'charset :us-ascii': 0.37; 'guys': 0.38; 'files': 0.38; 'data': 0.39; 'format': 0.39; 'application': 0.39; 'to:addr:python.org': 0.40; 'subject:with': 0.40; 'save': 0.60; 'your': 0.60; 'desk': 0.61; 'capture': 0.66; 'situation': 0.67; 'serial': 0.70; 'jul': 0.72; 'transfer': 0.73; 'subject:you': 0.85; 'dennis': 0.91; 'device,': 0.91; 'chapters': 0.93; 'received:108': 0.93 X-Injected-Via-Gmane: http://gmane.org/ X-Gmane-NNTP-Posting-Host: adsl-108-79-216-14.dsl.klmzmi.sbcglobal.net X-Newsreader: Forte Agent 6.00/32.1186 X-No-Archive: YES X-BeenThere: python-list@python.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: General discussion list for the Python programming language List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-Mailman-Original-Message-ID: <3lhbob1monp1ek1rvd3guies9tae7qas8d@4ax.com> X-Mailman-Original-References: Xref: csiph.com comp.lang.python:111374 On Tue, 12 Jul 2016 20:01:25 +0530, "Veek. M" declaimed the following: >My question is: how do you guys deal with a situation like this? Do you >look through the source code? Do you switch to scapy? Do you now look >for books on scapy - there are quite a few, with chapters covering it. > Me? For your application I'd likely just run Wireshark into a capture file, and then post process the capture... Though that WAS a painful process in a way. Capture in Wireshark pcapng format (a few GB of data) in the lab... transfer the capture to my desk machine... Use Wireshark to load the capture, filter it, then save it in an XML format (10x the GB)... Python program to read the XML and load the parts I needed into an SQLite3 database (0.5x the original GB). Then extract from database to Excel for plotting Wireshark did have capture formats that would normally have been easier -- but I needed the full precision time-stamp (my post processing was reading two capture files -- what was sent from one NIC to an external device, and what was received from that device on a separate NIC of the same computer, so the time-stamps were on the same basis -- matching up serial numbered data packets, and computing the time-delta latency). -- Wulfraed Dennis Lee Bieber AF6VN wlfraed@ix.netcom.com HTTP://wlfraed.home.netcom.com/