Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #28201 > unrolled thread
| Started by | Dave Angel <d@davea.name> |
|---|---|
| First post | 2012-09-01 00:40 -0400 |
| Last post | 2012-09-01 00:40 -0400 |
| Articles | 1 — 1 participant |
Back to article view | Back to comp.lang.python
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: to know binary Dave Angel <d@davea.name> - 2012-09-01 00:40 -0400
| From | Dave Angel <d@davea.name> |
|---|---|
| Date | 2012-09-01 00:40 -0400 |
| Subject | Re: to know binary |
| Message-ID | <mailman.22.1346474487.27098.python-list@python.org> |
On 09/01/2012 12:15 AM, contro opinion wrote: > there is a only line in the file nanmed test: > 1234 > when i open it whit xxd > xxd test > what i get is : > 0000000: 3132 3334 0a 1234. > can you explain it ? > > > Explain what, exactly? Explain why you were able to run xxd without first installing Mumps? What is it you don't understand? Do you know hex? Are you familiar with the hex codes for common ASCII characters and control characters? Does the period at the end of the line bother you? Are you expecting some different number of zeroes in the address field? Since you're apparently running Linux/Unix, you can find xxd executable by using where xxd. And you can tell what kind of file it is by running file on it. xxd is evidently not written in Python. So why again are you asking here? -- DaveA
Back to top | Article view | comp.lang.python
csiph-web