Not processing images - can we skip the creation of a local storage path

[lsemel]

We're not using Goose to process any images, but despite this it requires the existence of a local storage path, and complains if it can't write to the server's filesystem. I have to make sure /tmp/goose is always available and writable, and occasionally get errors from Goose complaining that it can't write some file there.

Is there a way to turn this feature off completely and never have Goose write to the local filesystem, even if it disables image processing?

[nathanathan]

There is a flag to disable image processing here:

python-goose/goose/configuration.py

Line 43 in 9c217d1

self.enable_image_fetching = True

However, it looks like the initialize function here (

python-goose/goose/__init__.py

Line 64 in 9c217d1

def initialize(self):

) will always check if it can write to the local storage folder and raise an error if it can't.

[nathanathan]

Here's the work around I'm using:

class FileFreeGoose(goose.Goose):
    def initialize(self):
        pass

FileFreeGoose({
  'parser_class':'soup',
  'enable_image_fetching' : False,
})

[grangier]

Hello,

Please test this branch and let me know if it suits your needs https://github.com/grangier/python-goose/tree/feature/access-local-84

xav

[nathanathan]

👍 Looks great!

[lsemel]

Looks good to me!

[grangier]

Should be fix in the latest head 6430e1d