hi, not sure if this is the best forum to ask, are you open to PR for adding linting ?
Hi @aucampia What kind of linting are you suggesting? We already require PEP8 compliant pull-requests, and we also strongly suggest all contributors use black on their code before creating a PR (though we don't enforce that).
We've had the discussion about linting many times in the past. The crux of the matter is we want to keep the barrier to contribution as low as possible for users of RDFLib. And the kinds of people who use RDFLib are not necessarily software engineers. We want researchers, academics, scientists, semantic extereprts, ontology experts, etc to be able to contribute to RDFLib. I don't like to stereotype or put people into categories, but in my experience a lot of experts do not want to deal with jumping through hoops to make their code compliant.
@ashleysommer thanks for the reply, and valid points. I was thinking PEP8, specifically autopep8, I guess I read right past it, but when I ran autopep8 on the codebase there were many warnings, so I guess I just assumed it was not being used, but I guess it makes sense to only apply it to pull requests.
@aucampia: you are right, there is a lot to do in the rdflib. We try our best in maintaining it and are happy about contributions to improve it.
Also there is some activity in improving the performance of th rdflib
recommendation of rdf4j and jena is not meant to be disparaging of rdflib, I also use rdflib mostly because most of the time I don't want to struggle with JVM and JVM does not have pip, pipx, etc - just don't want people to not use RDF because of a performance concern of rdflib
rdflib is awesome for what it is
but if I were to build something production grade that needs good performance I would use Jena or RDF4J
I think the best hope is to find more commercial applications for RDF
The more commercial use the more funding and more contributions
But if universities were better actors in the ecosystem it would help, if they instead direct resources to maintaining existing stuff instead of making yet another research project that will be abandoned it would be very beneificial
@aucampia: If you are planning to invest more time in performing big changes or something alike, we can also try to schedule a call with @ashleysommer and Nicholas to so how we can best organize this.
I am open to it, I want to help where I can but I don't really have dedicated time for it. For me it is easier to navigate the code base with type annotations. Besides this I am just looking at small issues to try and get a better understanding of the code base. I will look at the backlog for 6.0.0 where I can, some of it looks quite complicated, the RDF 1.1. test suite looks like a decent thing to try do and not that complicated, but I have not quite built up the courage for starting on that. Actual bug I will look at next is RDFLib/rdflib#1228
what is best is to just make sure milestone backlog is current and prioritized
But I think that is the case, or have no reason to think it is not the case
no but it does not inherit from unicode anymore, though the original problem may still be present yes
does @nicholascar come here?
If there are any PRs you want me to review I can have a look, I keep an eye out for small and easy ones where I have some knowledge about the implementation but the more complex ones I won't necessarily review unless someone makes an explicit request