Re: Django broken pipe error

2017-01-02 Thread justin walters
On Mon, Jan 2, 2017 at 6:14 AM, wrote: > > Thanks a lot Justin, > > The problem was solved when I employed standard Framework methods for > creation of new database object: > > in JS: > var trendModel = new App.TrendModel(); > trendModel.set("phrase", search_phrase); > trendModel.set("fro

Re: Django broken pipe error

2017-01-02 Thread dr . roman . graf
On Monday, December 12, 2016 at 6:38:39 PM UTC+1, justin walters wrote: > On Mon, Dec 12, 2016 at 7:27 AM, roma wrote: > > > Thanks Justin, > > > > I believe, the whole database story has no influence on the broken pipe > > error. I've commented out the who

Re: Django broken pipe error

2016-12-12 Thread justin walters
On Mon, Dec 12, 2016 at 7:27 AM, roma wrote: > Thanks Justin, > > I believe, the whole database story has no influence on the broken pipe > error. I've commented out the whole block and leave only return line: > return HttpResponse(res, content_type="text/plain; chars

Re: Django broken pipe error

2016-12-12 Thread roma
nd.delete() > > logger.info("delete old trend: %s. " % trend) > > except Trend.DoesNotExist: > > logger.info("create trend: %s. " % trend) > > trend.save() > > return trend_dict > > > > Thank you

Re: Django broken pipe error

2016-12-07 Thread justin walters
gt; except Trend.DoesNotExist: > logger.info("create trend: %s. " % trend) > trend.save() > return trend_dict > > Thank you in advance! > > Roman > -- > https://mail.python.org/mailman/listinfo/python-list > It looks like you can

Re: Django broken pipe error

2016-12-07 Thread dr . roman . graf
On Tuesday, December 6, 2016 at 3:22:13 PM UTC+1, dr.rom...@gmail.com wrote: > Hi, > > I'm facing strange Django broken pipe error (Python 2.7 on Ubuntu) that > apparently is a not fixed Django bug. Does anybody now how to fix it? I've > been searching a lot and

Re: Django broken pipe error

2016-12-06 Thread justin walters
On Tue, Dec 6, 2016 at 6:21 AM, wrote: > Hi, > > I'm facing strange Django broken pipe error (Python 2.7 on Ubuntu) that > apparently is a not fixed Django bug. Does anybody now how to fix it? I've > been searching a lot and didn't find any solution. > > Th

Django broken pipe error

2016-12-06 Thread dr . roman . graf
Hi, I'm facing strange Django broken pipe error (Python 2.7 on Ubuntu) that apparently is a not fixed Django bug. Does anybody now how to fix it? I've been searching a lot and didn't find any solution. This error happens very irregularly by Post request in Django. Sometimes it

Broken pipe from gevent/pywsgi.py

2016-05-03 Thread Larry Martell
thon2.7/dist-packages/gevent/socket.py", line 460, in sendall data_sent += self.send(_get_memory(data, data_sent), flags) File "/usr/local/lib/python2.7/dist-packages/gevent/socket.py", line 437, in send return sock.send(data, flags) error: [Errno 32] Broken pipe {

Re: Error 32 - Broken Pipe . Please Help!!

2012-09-05 Thread Mark Lawrence
On 05/09/2012 06:33, Dennis Lee Bieber wrote: On Tue, 4 Sep 2012 20:40:57 -0700 (PDT), Ramchandra Apte declaimed the following in gmane.comp.python.general: *Please* make your variable names more descriptive. No kidding... I haven't seen such cryptic names since 1972 -- an era when

Re: Error 32 - Broken Pipe . Please Help!!

2012-09-04 Thread Ramchandra Apte
te_packet > > sock.send(struct.pack("l", len(sent_data)) + sent_data) > > error: [Errno 32] Broken pipe > > > > Code : > > > > #code > > > > s=1 > > f=0 > > c=0 > > > > for i in range (1,1

Re: Error 32 - Broken Pipe . Please Help!!

2012-09-04 Thread Emile van Sebille
hell/monitor.py", line 575, in run already_pickled=True) File "/usr/lib/python2.7/dist-packages/spyderlib/utils/bsdsocket.py", line 24, in write_packet sock.send(struct.pack("l", len(sent_data)) + sent_data) error: [Errno 32] Broken pipe Code : So, what code is

Re: Error 32 - Broken Pipe . Please Help!!

2012-09-04 Thread Laszlo Nagy
s/externalshell/monitor.py", line 575, in run already_pickled=True) File "/usr/lib/python2.7/dist-packages/spyderlib/utils/bsdsocket.py", line 24, in write_packet sock.send(struct.pack("l", len(sent_data)) + sent_data) error: [Errno 32] Broken pipe Code : #code s=1 f

Error 32 - Broken Pipe . Please Help!!

2012-09-04 Thread Sreenath k
already_pickled=True) File "/usr/lib/python2.7/dist-packages/spyderlib/utils/bsdsocket.py", line 24, in write_packet sock.send(struct.pack("l", len(sent_data)) + sent_data) error: [Errno 32] Broken pipe Code : #code s=1 f=0 c=0 for i in range (1,100): c=0

Re: Broken pipe

2010-05-15 Thread Lie Ryan
On 05/15/10 11:56, Lawrence D'Oliveiro wrote: > In message <4bec2a9...@dnews.tpgi.com.au>, Lie Ryan wrote: > >> On 05/13/10 22:41, Lawrence D'Oliveiro wrote: >>> In message , Chris >>> Rebert wrote: >>> Also, please don't use semicolons in your code. It's bad style. >>> >>> Wonder why they’re

Re: Broken pipe

2010-05-14 Thread Lawrence D'Oliveiro
In message <4bec2a9...@dnews.tpgi.com.au>, Lie Ryan wrote: > On 05/13/10 22:41, Lawrence D'Oliveiro wrote: >> In message , Chris >> Rebert wrote: >> >>> Also, please don't use semicolons in your code. It's bad style. >> >> Wonder why they’re allowed, then. > > they're there for line continuatio

Re: Broken pipe

2010-05-13 Thread Lie Ryan
On 05/13/10 22:41, Lawrence D'Oliveiro wrote: > In message , Chris > Rebert wrote: > >> Also, please don't use semicolons in your code. It's bad style. > > Wonder why they’re allowed, then. they're there for line continuation, e.g.: a = 40; foo(a) but in many cases, putting two statements in

Re: Broken pipe

2010-05-13 Thread Lawrence D'Oliveiro
In message , Chris Rebert wrote: > Also, please don't use semicolons in your code. It's bad style. Wonder why they’re allowed, then. -- http://mail.python.org/mailman/listinfo/python-list

Re: Broken pipe

2010-05-07 Thread cerr
et(AF_INET, SOCK_STREAM); > > >> > data = string.join("NovaxTest",'\n'); > > >> > sock.send(data); > > >> > sock.close(); > > >> > and I'm calling this script like that: "./TestService.py 127.0.0.1 > > >

Re: Broken pipe

2010-05-07 Thread Ron Eggler
t;> > sock.close(); > >> > and I'm calling this script like that: "./TestService.py 127.0.0.1 > >> > 1514" but when I call it I get following back: > >> > sending data to 127.0.0.1:1514 > >> > data: NovaxTest > >> &

Re: Broken pipe

2010-05-06 Thread Chris Rebert
ring.join("NovaxTest",'\n'); >> > sock.send(data); >> > sock.close(); >> > and I'm calling this script like that: "./TestService.py 127.0.0.1 >> > 1514" but when I call it I get following back: >> > sending data t

Re: Broken pipe

2010-05-06 Thread Ron Eggler
is script like that: "./TestService.py 127.0.0.1 > > 1514" but when I call it I get following back: > > sending data to 127.0.0.1:1514 > > data: NovaxTest > > Traceback (most recent call last): > > File "./TestService.py", line 18, in > >sock.

Re: Broken pipe

2010-05-06 Thread Chris Rebert
t; data = string.join("NovaxTest",'\n'); > sock.send(data); > sock.close(); > and I'm calling this script like that: "./TestService.py 127.0.0.1 > 1514" but when I call it I get following back: > sending data to 127.0.0.1:1514 > data: NovaxTest >

Broken pipe

2010-05-06 Thread cerr
TestService.py 127.0.0.1 1514" but when I call it I get following back: sending data to 127.0.0.1:1514 data: NovaxTest Traceback (most recent call last): File "./TestService.py", line 18, in sock.send(data); socket.error: [Errno 32] Broken pipe I understand that UNIX sends an Err

Need help w 'Broken pipe' handling

2010-02-03 Thread gb345
obj, exc_tb): print >> sys.stderr, "excepthook called" sys.exit(0) signal(SIGPIPE, handle_sigpipe) signal(SIGINT, handle_sigint) # sys.excepthook = my_excepthook while True: try: print random.random() except IOError as (_, error): if error == 'Bro

Re: Spam Bot, broken pipe

2009-11-08 Thread Michael Torrie
Someone Something wrote: > I have a irc spam bot (only testing on my channel :P ) whose main loop is > the following: Poor choice of words on your part. Anything spam-related is evil and will not get a response. That said, "IRC bots" are certainly okay and common, and are useful tools. Some are

Re: Spam Bot, broken pipe

2009-11-07 Thread Someone Something
while True: >> > self.sock.send(privc=" :SPAM SPAM SPAM!"); >> > time.sleep(2); >> > >> > And it gives an error "Broken Pipe". >> > How can I fix this? >> >> By doing it right... unfortunaly I don't approve of spam and can >> therefor not tell you how to do that. >> > > > -- http://mail.python.org/mailman/listinfo/python-list

Spam Bot, broken pipe

2009-11-07 Thread Someone Something
l :P ) whose main loop is > > the following: > > > > privc="PRIVMSG "+self.channel > > while True: > > self.sock.send(privc=" :SPAM SPAM SPAM!"); > > time.sleep(2); > > > > And it gives an error "Broken Pipe". >

Spam Bot, broken pipe

2009-11-07 Thread Someone Something
I have a irc spam bot (only testing on my channel :P ) whose main loop is the following: privc="PRIVMSG "+self.channel while True: self.sock.send(privc=" :SPAM SPAM SPAM!"); time.sleep(2); And it gives an error "Broken Pipe". How can I fix this? --

Re: Debugging "broken pipe" (in telnetlib)

2007-07-04 Thread Samuel
Thanks for your comments, Jean-Paul. -- http://mail.python.org/mailman/listinfo/python-list

Re: Debugging "broken pipe" (in telnetlib)

2007-07-03 Thread Jean-Paul Calderone
On Tue, 03 Jul 2007 08:54:25 -0700, Samuel <[EMAIL PROTECTED]> wrote: >On Jul 3, 3:03 pm, Jean-Paul Calderone <[EMAIL PROTECTED]> wrote: >> EPIPE results when writing to a socket for which writing has been shutdown. >> This most commonly occurs when the socket has closed. You need to handle >> thi

Re: Debugging "broken pipe" (in telnetlib)

2007-07-03 Thread Samuel
On Jul 3, 3:03 pm, Jean-Paul Calderone <[EMAIL PROTECTED]> wrote: > EPIPE results when writing to a socket for which writing has been shutdown. > This most commonly occurs when the socket has closed. You need to handle > this exception, since you can't absolutely prevent the socket from being > cl

Re: Debugging "broken pipe" (in telnetlib)

2007-07-03 Thread Jean-Paul Calderone
On Tue, 03 Jul 2007 05:12:22 -0700, Samuel <[EMAIL PROTECTED]> wrote: >Hi, > >When using telnetlib, the connection sometimes breaks with the >following error: > >"error: (32, 'Broken pipe')" > >where the traceback points to > >s

Debugging "broken pipe" (in telnetlib)

2007-07-03 Thread Samuel
Hi, When using telnetlib, the connection sometimes breaks with the following error: "error: (32, 'Broken pipe')" where the traceback points to self.sock.send(buffer) in telnetlib.py. The problem is unreproducible, but happens fairly often (approx. 5% of the time). Any idea

Re: subprocess -- broken pipe error

2007-07-02 Thread Steve Holden
7stud wrote: > On Jul 2, 2:12 pm, Steve Holden <[EMAIL PROTECTED]> wrote: >> a) Who told you pipes should be unbuffered by default, and b) what difference >> does that make anyway? >> > > a) The docs. > > b) If the pipes were buffered then writing a small amount of data like > "text3" to the pipe

Re: subprocess -- broken pipe error

2007-07-02 Thread Steve Holden
7stud wrote: > On Jul 2, 1:58 pm, Bjoern Schliessmann [EMAIL PROTECTED]> wrote: >> 7stud wrote: >>> Thanks for the response. So are you saying that the only way you >>> can get data out of a pipe is when the subprocess has terminated? >> No, not only because Pipes aren't related to processes in a

Re: subprocess -- broken pipe error

2007-07-02 Thread 7stud
On Jul 2, 2:12 pm, Steve Holden <[EMAIL PROTECTED]> wrote: > a) Who told you pipes should be unbuffered by default, and b) what difference > does that make anyway? > a) The docs. b) If the pipes were buffered then writing a small amount of data like "text3" to the pipe would cause the other side

Re: subprocess -- broken pipe error

2007-07-02 Thread Steve Holden
7stud wrote: > Why doesn't the following program write to the file? > > driver.py > --- > import subprocess as sub > > p = sub.Popen(["python", "-u", "test1.py"], stdin=sub.PIPE, > stdout=sub.PIPE) > > > p.stdin.write("text3") > > while True: > pass > --- > > test1.py: > -

Re: subprocess -- broken pipe error

2007-07-02 Thread 7stud
On Jul 2, 2:03 pm, Bjoern Schliessmann wrote: > 7stud wrote: > > Why doesn't the following program write to the file? > > [...] > > It just hangs, and then when I hit Ctrl+C and look in the file, > > the data isn't in there. > > Also, the pipe may be unbuffered by > default; file access isn't. >

Re: subprocess -- broken pipe error

2007-07-02 Thread 7stud
On Jul 2, 1:58 pm, Bjoern Schliessmann wrote: > 7stud wrote: > > Thanks for the response. So are you saying that the only way you > > can get data out of a pipe is when the subprocess has terminated? > > No, not only because Pipes aren't related to processes in any > special way. > > He said that

Re: subprocess -- broken pipe error

2007-07-02 Thread Bjoern Schliessmann
7stud wrote: > Why doesn't the following program write to the file? > [...] > It just hangs, and then when I hit Ctrl+C and look in the file, > the data isn't in there. I suppose your running child process isn't closed cleanly if you terminate the parent process. Also, the pipe may be unbuffered

Re: subprocess -- broken pipe error

2007-07-02 Thread Bjoern Schliessmann
7stud wrote: > Thanks for the response. So are you saying that the only way you > can get data out of a pipe is when the subprocess has terminated? No, not only because Pipes aren't related to processes in any special way. He said that you can't write to a pipe whose reader has already terminat

Re: subprocess -- broken pipe error

2007-07-02 Thread 7stud
Why doesn't the following program write to the file? driver.py --- import subprocess as sub p = sub.Popen(["python", "-u", "test1.py"], stdin=sub.PIPE, stdout=sub.PIPE) p.stdin.write("text3") while True: pass --- test1.py: - import sys data = sys.stdin.read() f = open("a

Re: subprocess -- broken pipe error

2007-07-02 Thread 7stud
On Jul 2, 11:32 am, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote: > On Jul 2, 1:12 pm, 7stud <[EMAIL PROTECTED]> wrote: > > > > > Hi, > > > Can someone explain what a broken pipe is? The following produces a > > broken pipe error: > >

Re: subprocess -- broken pipe error

2007-07-02 Thread [EMAIL PROTECTED]
On Jul 2, 1:12 pm, 7stud <[EMAIL PROTECTED]> wrote: > Hi, > > Can someone explain what a broken pipe is? The following produces a > broken pipe error: > > -- > import subprocess as sub > > p = sub.Popen(["ls", "-al", "../&q

subprocess -- broken pipe error

2007-07-02 Thread 7stud
Hi, Can someone explain what a broken pipe is? The following produces a broken pipe error: -- import subprocess as sub p = sub.Popen(["ls", "-al", "../"], stdin=sub.PIPE, stdout=sub.PIPE) print p.stdout.read() #outputs the files correctly p.stdin.wri

Re: Broken pipe with os.popen3()

2007-04-10 Thread Thomas Guettler
Christoph Krammer wrote: > Hello everybody, > > I try to use an external OCR tool to convert some binary image data to > text. The image is in one variable, the text should be converted to > another. I use the following code: > > (si, so, se) = os.popen3('ocrad') > si.write(frame) > si.close

Broken pipe with os.popen3()

2007-04-10 Thread Christoph Krammer
This code leads to a broken pipe error. I think this is because of the command already writing data to stdout after getting the first part of the input. But when I change the order of the code lines, i.e. opening the reading pipe so before writing to si, the program hangs, because no data is written

Re: socket.error: (32, 'Broken pipe'): need help

2005-10-27 Thread Jeremy Jones
ingMsg) >socket.error: (32, 'Broken pipe') > >I do not know where to start with? > >Thanks >Junhua > > Can you tell if the recipient actually got any of the data? At what point do you get this error? Is the client able to connect to the server? Could you extract

Re: socket.error: (32, 'Broken pipe'): need help

2005-10-27 Thread dcrespo
When enabling the server, note that you put '' as the IP, and not 'localhost'. if you put an ip: '172.16.1.2', your server will listen on that IP (if it's valid) if you put '', your server will listen on all IPs defined on that computer. of you put 'localhost', it will listen for local connections

socket.error: (32, 'Broken pipe'): need help

2005-10-27 Thread Junhua Deng (AL/EAB)
Hi, I have a simple server-client application with threading. It works fine when both server and client on the same machine, but I get the following error message if the server is on another machine: ... ... self.socket.send(outgoingMsg) socket.error: (32, 'Broken pipe') I d