set_extension() got an unexpected keyword argument 'force'

[elisasongintegr8]

Hi,

I've followed your instruction, but got an error msg: set_extension() got an unexpected keyword argument 'force'

Can you pls help me with that?

[elisasongintegr8]

I found the problem: in spacy, Token.set_extension doesn't have 'force' as input.

https://spacy.io/api/token

[Liebeck]

What is your spaCy version? They introduced the force parameter in 2.0.3, I think. According to https://github.com/explosion/spaCy/blob/master/spacy/tokens/token.pyx#L31-L34 and https://github.com/explosion/spaCy/blob/master/spacy/errors.py#L238-L239 the force parameter should still be in use.

[elisasongintegr8]

Hi, thanks for your msg. My spacy version is 2.0.10
I deleted the ‘force’, and I don’t have any problem with your script anymore.

On Aug 27, 2018, at 4:28 PM, Matthias Liebeck notifications@github.com wrote:

What is your spaCy version? They introduced the force parameter in 2.0.3, I think. According to https://github.com/explosion/spaCy/blob/master/spacy/tokens/token.pyx#L31-L34 https://github.com/explosion/spaCy/blob/master/spacy/tokens/token.pyx#L31-L34 and https://github.com/explosion/spaCy/blob/master/spacy/errors.py#L238-L239 https://github.com/explosion/spaCy/blob/master/spacy/errors.py#L238-L239 the force parameter should still be in use.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/Liebeck/spacy-sentiws/issues/1#issuecomment-416245425, or mute the thread https://github.com/notifications/unsubscribe-auth/Ae1hcIUbrS3rgRb_eBhm1WrXHBa3W_ELks5uVAIPgaJpZM4WNpfW.

[Liebeck]

Ok, percect. Might be related to https://github.com/explosion/spaCy/issues/2073 which was fixed in 2.0.11

I had to use the force parameter since I created multiple pipeline instances and there was an issue with settings extensions globally