Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Trying to upload python requirements.txt file, #48

Open
miketheman opened this issue Jun 8, 2017 · 2 comments
Open

Trying to upload python requirements.txt file, #48

miketheman opened this issue Jun 8, 2017 · 2 comments

Comments

@miketheman
Copy link

$ gemnasium dependency_files p --files=packages.txt
Sending files to Gemnasium: json: cannot unmarshal string into Go value of type models.DependencyFile

File has 204 line in it, some are package names like:

Django==1.9.13

Others like:

-e git+https://github.com/evonove/django-oauth-toolkit.git@707a6016a3023fe423ede53db707c55273b0f6d0#egg=django_oauth_toolkit

Removing the https lines returns the same error.

Is there a requirement that the text files be named with requirements in them?

@miketheman
Copy link
Author

@gravis Any ideas?

@fcat
Copy link

fcat commented Oct 6, 2017

The short answer is: yes, Python requirements files should be named either requirements.txt or requires.txt. Renaming the file or using a symlink should fix the problem.

If you still have issues after renaming the file, please contact us via http://support.gemnasium.com. All we need is the project slug and the approximate time you last tried to upload the dependency files of your projects.

That said, there's a mismatch here because Gemnasium.com returns HTTP 200 (or 204) along with something that can't be unmarshalled into a map[string][]DependencyFile. In a word, Toolbelt got something it didn't expect. See dependency_files.go.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants