I've granted you contributor permissions.
However, it's unclear whether revision commenting is included in those
rights or not.

Let me know if it works for you.

-Pierre

2013/2/23 Sylvain Corlay <[email protected]>:
> Hello, would it be possible to obtain the privileges to comment on
> revisions/issues?
>
>
> On Wednesday, February 20, 2013 12:42:21 AM UTC-5, Jed Ludlow wrote:
>>
>> I went ahead and created an issue for this here:
>>
>> http://code.google.com/p/spyderlib/issues/detail?id=1275
>>
>>
>> On Tue, Feb 19, 2013 at 6:15 AM, Sylvain Corlay <[email protected]>
>> wrote:
>>>
>>> Hi Carlos,
>>> I don't know much about POSIX but I searched a bit and found out that
>>> this error code was (EINTR). It seems that one should try again the system
>>> call until it is successful. There are some similar workarounds in pypy:
>>> https://github.com/pypy/pypy/blob/master/lib-python/2.7/socket.py. (look for
>>> EINTR). I hope this solve your socket errors.
>>> S.
>>>
>>>
>>> On Tuesday, February 19, 2013 6:35:26 AM UTC-5, Carlos Córdoba wrote:
>>>>
>>>> Hi Sylvain,
>>>>
>>>> How do you come up with those patches? In particular, what do these
>>>> lines mean?
>>>>
>>>> if e.args[0] == 4:
>>>>      continue
>>>>
>>>> I don't understand what are the types of errors you're getting but I've
>>>> seen our infamous socket errors reappear again, although only sporadically.
>>>>
>>>> Cheers,
>>>> Carlos
>>>>
>>>> El 18/02/13 16:52, Sylvain Corlay escribió:
>>>>
>>>> Here is a quick fix that solved the problem for me.
>>>>
>>>> I attached the diff files for spyderlib/spyder.py and
>>>> spyderlib/widgets/externalshell/introspection.py
>>>>
>>>> Cheers,
>>>>
>>>> Sylvain
>>>>
>>>> On Monday, February 18, 2013 4:08:22 PM UTC-5, Sylvain Corlay wrote:
>>>>>
>>>>> I tried to debug it but the bug does not occur when debugging and
>>>>> ipython consoles are correctly opened.
>>>>> S.
>>>>>
>>>>> On Monday, February 18, 2013 3:51:56 PM UTC-5, Sylvain Corlay wrote:
>>>>>>
>>>>>> Everything in 64 bits
>>>>>>
>>>>>> ipython 0.13.1, (from ppa
>>>>>> https://launchpad.net/~jtaylor/+archive/ipython)
>>>>>> pyflakes 0.5.0,
>>>>>> rope 0.9.2,
>>>>>> python 2.7.3,
>>>>>> qt 4.8.1
>>>>>> python-qt4 4.9.1
>>>>>>
>>>>>> S.
>>>>>>
>>>>>> On Monday, February 18, 2013 1:47:00 PM UTC-5, ufechner wrote:
>>>>>>>
>>>>>>> Hi,
>>>>>>>
>>>>>>> I cannot reproduce this problem on Ubuntu 12.04, 32 bits.
>>>>>>>
>>>>>>> I am using revision dd4a10611038, beta2, pyflakes 0.6.1, rope 0.9.4
>>>>>>> Python 2.7.3 32 bits, Qt 4.8.1, PyQt4 (API v2) 4.9.1.
>>>>>>>
>>>>>>> Everything is working fine, only that I still see a double prompt
>>>>>>> when
>>>>>>> debugging with the toolbar, but that is another little problem.
>>>>>>>
>>>>>>> I am using the following script to launch spyder:
>>>>>>>
>>>>>>> LD_LIBRARY_PATH='/usr/lib/atlas-base/'
>>>>>>> export
>>>>>>> PYTHONPATH=$PYTHONPATH:/home/ufechner/00Software/spyder-2.2/spyderlib
>>>>>>> python
>>>>>>> /home/ufechner/00Software/spyder-2.2/spyderlib/spyderlib/spyder.py
>>>>>>>
>>>>>>> I forgot to mention that I am using ipython version 0.13.1, installed
>>>>>>> with easy_install -U ipython.
>>>>>>>
>>>>>>>
>>>>>>> Best regards:
>>>>>>>
>>>>>>> Uwe Fechner
>>>>>>>
>>>>>>> Am 18.02.2013 17:35, schrieb Sylvain Corlay:
>>>>>>>
>>>>>>> Hi,
>>>>>>>
>>>>>>> It seems that under Ubuntu 12.04 64 bits, spyder fails to open new
>>>>>>> IPython consoles. It does start a new kernel in the "Console" widget 
>>>>>>> but no
>>>>>>> console is opened in the "IPython Console" widget. However, I can still 
>>>>>>> use
>>>>>>> a "connect to an existing kernel" to connect to it. A traceback is 
>>>>>>> produced
>>>>>>> in the internal console:
>>>>>>>
>>>>>>>> Exception in thread Thread-2:
>>>>>>>> Traceback (most recent call last):
>>>>>>>>   File "/usr/lib/python2.7/threading.py", line 551, in
>>>>>>>> __bootstrap_inner
>>>>>>>>     self.run()
>>>>>>>>   File "spyderlib/spyderlib/widgets/externalshell/introspection.py",
>>>>>>>> line 62, in run
>>>>>>>>     conn, _addr = sock.accept()
>>>>>>>>   File "/usr/lib/python2.7/socket.py", line 202, in accept
>>>>>>>>     sock, addr = self._sock.accept()
>>>>>>>> error: [Errno 4] Interrupted system call
>>>>>>>>
>>>>>>>> Exception in thread Thread-3:
>>>>>>>> Traceback (most recent call last):
>>>>>>>>   File "/usr/lib/python2.7/threading.py", line 551, in
>>>>>>>> __bootstrap_inner
>>>>>>>>     self.run()
>>>>>>>>   File "spyderlib/spyderlib/widgets/externalshell/introspection.py",
>>>>>>>> line 62, in run
>>>>>>>>     conn, _addr = sock.accept()
>>>>>>>>   File "/usr/lib/python2.7/socket.py", line 202, in accept
>>>>>>>>     sock, addr = self._sock.accept()
>>>>>>>> error: [Errno 4] Interrupted system call
>>>>>>>>
>>>>>>>> Exception in thread Thread-4:
>>>>>>>> Traceback (most recent call last):
>>>>>>>>   File "/usr/lib/python2.7/threading.py", line 551, in
>>>>>>>> __bootstrap_inner
>>>>>>>>     self.run()
>>>>>>>>   File "/usr/lib/python2.7/threading.py", line 504, in run
>>>>>>>>     self.__target(*self.__args, **self.__kwargs)
>>>>>>>>   File "spyderlib/spyderlib/spyder.py", line 1856, in
>>>>>>>> start_open_files_server
>>>>>>>>     req, addr = self.open_files_server.accept()
>>>>>>>>   File "/usr/lib/python2.7/socket.py", line 202, in accept
>>>>>>>>     sock, addr = self._sock.accept()
>>>>>>>> error: [Errno 4] Interrupted system call
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> (When trying revisions older than 4a06c308b99d (Fixed crash at
>>>>>>> startup occuring when restoring Project Explorer's tree view), spyder
>>>>>>> crashes at startup. However I did not have this issue before. I can 
>>>>>>> avoid
>>>>>>> this problem by deleting the configuration folder .spyder2 that does not
>>>>>>> seem to work with older versions. )
>>>>>>>
>>>>>>> It is odd because I did not have this ipython console issue in the
>>>>>>> past with the corresponding revisions. Although there has been a few
>>>>>>> packages updated in the meanwhile.
>>>>>>>
>>>>>>> Thanks,
>>>>>>>
>>>>>>> S.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> You received this message because you are subscribed to the Google
>>>>>>> Groups "spyder" group.
>>>>>>> To unsubscribe from this group and stop receiving emails from it,
>>>>>>> send an email to [email protected].
>>>>>>> To post to this group, send email to [email protected].
>>>>>>> Visit this group at http://groups.google.com/group/spyderlib?hl=en.
>>>>>>> For more options, visit https://groups.google.com/groups/opt_out.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>> --
>>>> You received this message because you are subscribed to the Google
>>>> Groups "spyder" group.
>>>> To unsubscribe from this group and stop receiving emails from it, send
>>>> an email to [email protected].
>>>> To post to this group, send email to [email protected].
>>>> Visit this group at http://groups.google.com/group/spyderlib?hl=en.
>>>> For more options, visit https://groups.google.com/groups/opt_out.
>>>>
>>>>
>>>>
>>>>
>>> --
>>> You received this message because you are subscribed to the Google Groups
>>> "spyder" group.
>>> To unsubscribe from this group and stop receiving emails from it, send an
>>> email to [email protected].
>>> To post to this group, send email to [email protected].
>>> Visit this group at http://groups.google.com/group/spyderlib?hl=en.
>>> For more options, visit https://groups.google.com/groups/opt_out.
>>>
>>>
>>
>>
> --
> You received this message because you are subscribed to the Google Groups
> "spyder" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> To post to this group, send email to [email protected].
> Visit this group at http://groups.google.com/group/spyderlib?hl=en.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"spyder" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/spyderlib?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to