On 02/26/2015 10:21 AM, Andreas Roehler wrote:
> On 26.02.2015 18:28, Justin wrote:
>> The first issue is fixed (I probably should have filed two separate bug
>> reports (and can still do so if tha tis convenient)) but the second
>> issue remains. However, it is very strange. To elaborate, if I do
>>
>> [1] np.asa[TAB]
>>
>> np.asarray is a possible completion
>>
>> However, if I do
>>
>> [2] np.asar[TAB]
>>
>> it automaticaly compeletes to np.asarray_chkfinite
>>
>> Furthermore, this seems to be the only function where I see this strange
>> behavior.
>>
>> I **think** I ran the test but list is pretty foreign to me so if I didn't do it correctly, please
>> let me know. Otherwise, here are the results:
>>
>> Selector: py-ert-socket-modul-completion-lp-1284141
>> Passed: 0
>> Failed: 1 (1 unexpected)
>> Total: 1/1
>>
>> Started at: 2015-02-26 09:17:13-0800
>> Finished.
>> Finished at: 2015-02-26 09:17:13-0800
>>
>>
>> py-ert-socket-modul-completion-lp-1284141
>> (void-function py-test-with-temp-buffer)Selector: py-ert-socket-modul-completion-lp-1284141
>> Passed: 0
>> Failed: 1 (1 unexpected)
>> Total: 1/1
>>
>> Started at: 2015-02-26 09:17:13-0800
>> Finished.
>> Finished at: 2015-02-26 09:17:13-0800
>>
>>
>> py-ert-socket-modul-completion-lp-1284141
>> (void-function py-test-with-temp-buffer)
>>
> Defined at top of the file.
>
Ok, I think I got it this time:
Test py-ert- socket- modul-completio n-lp-1284141 backtrace: indent- or-complete) current- buffer (set-buffer temp-buffer) (unwind-protect (progn new-buffer " *temp*"))) (save-current-b new-buffer " *temp*"))) (sa code("\ 306\307! q\210\ 310\216\ 311 \312\216\ 313\314\ 315\316\ 3 -run-test- internal( [cl-struct- ert--test- execution- info [cl-struc code("\ 306\307! \211\211 r\310\311! q\210\312 d\313\223)L\210)\3 run-test( [cl-struct- ert-test py-ert- socket- modul-completio n-lp-1 run-or- rerun-test( [cl-struct- ert--stats t [[cl-struct- ert-test p run-tests- batch(nil) run-tests- batch-and- exit() line-1( ("-l" "ert" "-l" "py-ert-tests-1.el" "-f" "ert-run-te top-level( ) socket- modul-completio n-lp-1284141 condition: or-complete) socket- modul-completio n-lp-1284141 indent- offset, using defaults: 4
(py-
(let ((py-debug-p t) (py-shell-name "python") oldbuf) (if py-debug-p
(let (hs-minor-mode) (python-mode) (insert "import socket\nsocket.")
(progn (let (hs-minor-mode) (python-mode) (insert "import socket\nso
(unwind-protect (progn (let (hs-minor-mode) (python-mode) (insert "i
(save-
(let ((temp-buffer (generate-
(lambda nil (let ((temp-buffer (generate-
byte-
ert-
byte-
ert-
ert-
ert-run-tests(t #[(event-type &rest event-args) "\30\307\"\203G \
ert-
ert-
command-
command-line()
normal-
Test py-ert-
(void-function py-indent-
FAILED 27/29 py-ert-
Can't guess python-
On 02/26/2015 10:21 AM, Andreas Roehler wrote: chkfinite socket- modul-completio n-lp-1284141 socket- modul-completio n-lp-1284141 with-temp- buffer) Selector: py-ert- socket- modul-completio n-lp-1284141 socket- modul-completio n-lp-1284141 with-temp- buffer)
> On 26.02.2015 18:28, Justin wrote:
>> The first issue is fixed (I probably should have filed two separate bug
>> reports (and can still do so if tha tis convenient)) but the second
>> issue remains. However, it is very strange. To elaborate, if I do
>>
>> [1] np.asa[TAB]
>>
>> np.asarray is a possible completion
>>
>> However, if I do
>>
>> [2] np.asar[TAB]
>>
>> it automaticaly compeletes to np.asarray_
>>
>> Furthermore, this seems to be the only function where I see this strange
>> behavior.
>>
>> I **think** I ran the test but list is pretty foreign to me so if I didn't do it correctly, please
>> let me know. Otherwise, here are the results:
>>
>> Selector: py-ert-
>> Passed: 0
>> Failed: 1 (1 unexpected)
>> Total: 1/1
>>
>> Started at: 2015-02-26 09:17:13-0800
>> Finished.
>> Finished at: 2015-02-26 09:17:13-0800
>>
>>
>> py-ert-
>> (void-function py-test-
>> Passed: 0
>> Failed: 1 (1 unexpected)
>> Total: 1/1
>>
>> Started at: 2015-02-26 09:17:13-0800
>> Finished.
>> Finished at: 2015-02-26 09:17:13-0800
>>
>>
>> py-ert-
>> (void-function py-test-
>>
> Defined at top of the file.
>