building python for qnx 6.5
friends I am interested in python3 for QNX 6.5. Since i have not found a prebuilt distribution, I would like to build it. I wanted to find out how I could use Momentics IDE to build python for different targets. I want to build only for x86 right now but may want to build for the ARM target as well. The IDE is hosted on a windows platform. Momentics is based on eclipse I believe. any pointers would be deeply appreciated. thanks, srini -- https://mail.python.org/mailman/listinfo/python-list
Binary data exchange
friends
I have a pair of simple python programs as follows:
#!/usr/bin/python
# broadcast.py
import socket
from ctypes import *
import random
class PurgeData(Structure):
_fields_ = [(press,c_int), (ticks,c_int), (volume,c_float)]
myPort = 10756
sock=socket.socket(socket.AF_INET,socket.SOCK_DGRAM)
addr = ('localhost',myPort)
#sock.sendto(data,addr)
presdata = PurgeData()
presdata.press = 0
presdata.ticks = 100
for msg in range(1,20):
presdata.press = presdata.press+1
presdata.ticks = presdata.ticks+1
presdata.volume = random.random()
sock.sendto(presdata,addr)
#
#!/usr/bin/python
# Receiver
import socket
from ctypes import *
class PurgeData(Structure):
_fields_ = [(press,c_int), (ticks,c_int), (volume,c_float)]
myPort = 10756
sock=socket.socket(socket.AF_INET,socket.SOCK_DGRAM)
addr = ('localhost',myPort)
sock.bind(addr)
presdata=PurgeData()
while True:
data,addr = sock.recvfrom(1024)
memmove(addressof(presdata),data.strip(),len(data.strip()))
print presdata.press, presdata.ticks, presdata.volume
-
When I tried to run this I get some bizarre results:
1 101 0.343009024858
2 102 0.36397305131
3 103 0.495895296335
4 104 0.372055351734
5 105 0.933839201927
6 106 0.931187808514
7 107 0.876732826233
8 108 0.298638045788
1828716544 -754974720 0.183644190431
1845493760 1660944384 0.186560109258
1862270976 1056964608 0.18631502986
1879048192 1728053248 0.186902835965
1895825408 2097152000 0.18658298254
14 114 0.407857120037
15 115 0.833854913712
16 116 0.00646247947589
17 117 0.297783941031
18 118 0.58082228899
19 119 0.61717569828
the received data for the messages 9 thru 13 are not as expected.
I wonder if anyone can see what I am doing wrong?
Appreciate any hints. thanks, srini
--
https://mail.python.org/mailman/listinfo/python-list
Re: Binary data exchange
BTW - My environment is: H:\python Enthought Canopy Python 2.7.6 | 64-bit | (default, Apr 11 2014, 20:31:44) [MSC v .1500 64 bit (AMD64)] on win32 Type help, copyright, credits or license for more information. -- https://mail.python.org/mailman/listinfo/python-list
Re: Binary data exchange
Of course Cut and paste issue. Anyhow, i will look at the struct module.
cheers, srini
On Thursday, May 29, 2014 7:09:21 PM UTC-4, MRAB wrote:
On 2014-05-29 23:08, rasikasriniva...@gmail.com wrote:
friends
I have a pair of simple python programs as follows:
#!/usr/bin/python
# broadcast.py
import socket
from ctypes import *
import random
class PurgeData(Structure):
_fields_ = [(press,c_int), (ticks,c_int), (volume,c_float)]
myPort = 10756
sock=socket.socket(socket.AF_INET,socket.SOCK_DGRAM)
addr = ('localhost',myPort)
#sock.sendto(data,addr)
presdata = PurgeData()
presdata.press = 0
presdata.ticks = 100
for msg in range(1,20):
presdata.press = presdata.press+1
presdata.ticks = presdata.ticks+1
presdata.volume = random.random()
sock.sendto(presdata,addr)
#
#!/usr/bin/python
# Receiver
import socket
from ctypes import *
class PurgeData(Structure):
_fields_ = [(press,c_int), (ticks,c_int), (volume,c_float)]
myPort = 10756
sock=socket.socket(socket.AF_INET,socket.SOCK_DGRAM)
addr = ('localhost',myPort)
sock.bind(addr)
presdata=PurgeData()
while True:
data,addr = sock.recvfrom(1024)
memmove(addressof(presdata),data.strip(),len(data.strip()))
print presdata.press, presdata.ticks, presdata.volume
-
When I tried to run this I get some bizarre results:
1 101 0.343009024858
2 102 0.36397305131
3 103 0.495895296335
4 104 0.372055351734
5 105 0.933839201927
6 106 0.931187808514
7 107 0.876732826233
8 108 0.298638045788
1828716544 -754974720 0.183644190431
1845493760 1660944384 0.186560109258
1862270976 1056964608 0.18631502986
1879048192 1728053248 0.186902835965
1895825408 2097152000 0.18658298254
14 114 0.407857120037
15 115 0.833854913712
16 116 0.00646247947589
17 117 0.297783941031
18 118 0.58082228899
19 119 0.61717569828
the received data for the messages 9 thru 13 are not as expected.
I wonder if anyone can see what I am doing wrong?
Appreciate any hints. thanks, srini
I don't understand why you're using the .strip method. That's for
stripping whitespace from text, but you're not sending and receiving
text, you're sending and receiving binary data.
Personally, I'd use the struct module.
--
https://mail.python.org/mailman/listinfo/python-list
Re: ifconfig in python
On Jan 20, 7:33 am, Mark Wooding m...@distorted.org.uk wrote:
Дамјан Георгиевски gdam...@gmail.com writes:
Something *like* this could work:
myip = urllib2.urlopen('http://whatismyip.org/').read()
This is going to cause all manner of problems.
Firstly, many users are stuck behind NAT routers. In this case, the
external service will report the address of the router, which is
probably useless -- certainly it will be for programs attempting to
communicate over a LAN.
Secondly, imagine the joy when overzealous ISPs decide that
whatismyip.org is peddling kiddiepr0n (as happened to Wikipedia last
month): then the service will report the address of ISP's censoring
proxy to thousands of otherwise unrelated users.
And that's before we get onto onion routers like Tor...
Here's an idea which might do pretty well.
In [1]: import socket as S
In [2]: s = S.socket(S.AF_INET, S.SOCK_DGRAM)
In [4]: s.connect(('192.0.2.1', 666))
In [5]: s.getsockname()
Out[5]: ('172.29.198.11', 46300)
(No packets were sent during this process: UDP `connections' don't need
explicit establishment. The network 192.0.2.0/24 is reserved for use in
examples; selecting a local address should therefore exercise the
default route almost everywhere. If there's a specific peer address or
network you want to communicate with, use that address explicitly.)
I have to wonder what the purpose of this is. It's much better to have
the recipient of a packet work out the sender's address from the packet
(using recvfrom or similar) because that actually copes with NAT and so
on properly.
-- [mdw]
one way to get your head around this is - IP Addresses are associated
with the interface and not the computer. distinction may be subtle but
critical.
--
http://mail.python.org/mailman/listinfo/python-list
