On Apr 24, 2014, at 4:23 AM, Nikolaus Rath <[email protected]> wrote:
> Hi Diogo,
>
> Let's keep the discussion the list please.
Sorry, I just replied to the email (didn't notice it was sent just to you).
Isn't there an option to set the Reply-To in the mailing list?
>
> On 04/23/2014 02:19 AM, Diogo Vieira wrote:
>>>> Sorry to bother once again about this but I installed the 2.8.1
>>>> version in my machine (so far I was working with 2.7 version on a
>>>> folder on my home directory) but even after I edited the
>>>> __init__.py and added my custom backend to the library's
>>>> backends folderI still get "No such backend" when trying to mount
>>>> a filesystem.
>>>>
>>>> Already tried to remove the __pycache__ folders but it seems to
>>>> have made no effect. Am I missing something here?
>>>
>>> The usual things: exact error message, the commands you entered,
>>> the changes that you made to the code, etc.
>>
>> Well, the error message is the one I mentioned "No such backend:
>> <backend_name>". The command used was "mount.s3ql
>> <backend_name>://<bucket>/<prefix>/ <mountpoint>" and the only change
>> I made in the code was in
>> /usr/lib64/python3.3/site-packages/s3ql/backends/__init__.py (added
>> my backend name). The only thing I did then was to put my backend in
>> /usr/lib64/python3.3/site-packages/s3ql/backends/.
>>
>> So far I've been working with the source code downloaded from the
>> website in a folder on my home directory and I was able to add it
>> without any issues, even tough it was version 2.7.
>
> I don't believe this is due to the upgrade to 2.7. Can you confirm that
> it still works if you install S3QL 2.7 in
> /usr/lib64/python3.3/site-packages/ instead?
>
> My guess is that, in addition to upgrading, you also changed your
> backend, and now it cannot be imported anymore. What happens if you run
> 'python3 -c 'import s3ql.backends.yourmodule'?
I don't know how could I forget to try that. It clearly shows where's the
problem:
Traceback (most recent call last):
File "<string>", line 1, in <module>
File "/usr/lib64/python3.3/site-packages/s3ql/backends/eds.py", line
12, in <module>
from .common import (AbstractBackend, NoSuchObject, retry,
retry_generator, ImportError: cannot import name is_temp_network_error
With a quick look through the source code I believe you moved
is_temp_network_error to the dugong package right? Should I just change the
import from common to dugong?
Thank you for your help,
Diogo Vieira
--
You received this message because you are subscribed to the Google Groups
"s3ql" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
