Wrong package version

[pastet89]

Using pipreqs I got: Django==2.1.5 while my version was Django==2.0.

[uxlsl]

base on the code pipreqs.py 200 line ,it always return the new version!

       result.append({'name': item, 'version': data.latest_release_id})

[pastet89]

Well, interesting finding! However, isn't this supposed to be an unexpected behavior?

[uxlsl]

so caution while using!

[pastet89]

I suggest that this ia changed in later versions. If I try to fix it and contribute to the project, will @bndr accept my contribution?

На ср, 13 март 2019 г., 5:44 uxlsl [email protected] написа:

so caution while using!

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/bndr/pipreqs/issues/158#issuecomment-472268194, or mute the thread https://github.com/notifications/unsubscribe-auth/AHH4ARcH6hZjhTWzxXOC9e3UBo4MCIGNks5vWHQJgaJpZM4bXdPJ .

[neopostmodern]

I'd strongly recommend to change the behavior to what @pastet89 suggests, I'd guess that this is what most people assume when saving requirements. The goal most people pursue is probably to have a reproducible install on another machine.

[imlison]

I think using the --use-local option is the safest.