Code Monkey home page Code Monkey logo

Comments (10)

cyrus avatar cyrus commented on April 27, 2024

I vote to move the integers to the underscored attributes. I use them less often, so it will save my left pinky a lot of work!

from spacy.

transcranial avatar transcranial commented on April 27, 2024

I agree, I think it would be more intuitive to have the integer value as the underscored name rather than as the main name.

from spacy.

suchow avatar suchow commented on April 27, 2024

👍 on swapping them.

from spacy.

florijanstamenkovic avatar florijanstamenkovic commented on April 27, 2024

I don't think they should be swapped. While I would prefer to have ints underscored, changing it now breaks the API, and it is really not a very difficult convention to get used to.

from spacy.

syllog1sm avatar syllog1sm commented on April 27, 2024

I get that it breaks the API, and this is unfortunate. But I'd rather introduce breaking changes now than live with them forever.

from spacy.

florijanstamenkovic avatar florijanstamenkovic commented on April 27, 2024

Sure...

Also, after some more consideration, I think that having ints as default values for each tag makes a lot of sense since most of the time it's ints one wants to work with, and not unicode strings.

from spacy.

viksit avatar viksit commented on April 27, 2024

Yeah, agreed that the keyword_ should represent ints and keyword should be the string value. It's going to cause some pain to change APIs though 🎱

from spacy.

NSchrading avatar NSchrading commented on April 27, 2024

I guess I would vote for the change as well. When I first started using spaCy, I was initially confused why using .lemma/.lower/etc was giving me a number and not a string as expected. I think it makes more sense for the string value to be named "foo", and the integer value to be named "foo_", especially for new users.

from spacy.

ms8r avatar ms8r commented on April 27, 2024

Two weeks ago I would have said "yes, please swap" but now I'm thinking "please keep as is". The reason is less that I got used to it but more that my work focus has shifted from "data exploration" to "data processing". For the exploratory work the underscores where a bit of a pain but for the processing (which I believe will be the bigger portion) the current convention makes perfect sense.

from spacy.

lock avatar lock commented on April 27, 2024

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

from spacy.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.