Re:Analyzing Django requirement files on GitHub
by jayfk on Thursday June 08, 2017 @01:25PM
(#14515624)
The query I ran against the GitHub dataset has no activity/age/popularity data, just plain requirements files.
I'll write a follow up post on this :)
Re:Analyzing Django requirement files on GitHub
by Alex3917 on Thursday June 08, 2017 @01:31PM
(#14515651)
I'd add in a minimum of 100 or so stars also. Anything less than that is probably a personal project and not a package.
Re:Analyzing Django requirement files on GitHub
by ryanar on Friday June 09, 2017 @07:55AM
(#14520753)
Eh, that would miss my two stars django package then.[1] 100 is steep, and django packages are almost universally titled django-project-name so you could just find repos starting with django- with recent commits
Re:Analyzing Django requirement files on GitHub
by howderek on Thursday June 08, 2017 @06:31PM
(#14517667)
You may be interested in the GHTorrent database on BigQuery:
Re:Analyzing Django requirement files on GitHub
by adisbladis on Thursday June 08, 2017 @09:31PM
(#14518587)
I would also be interested in seeing if a project has any significant amount of stars to filter out "homework assignments" that likely doesn't see any real use.
Jay (at PyUp) - any idea?