Open brifordwylie opened 8 years ago
$ pip list | grep py2deb py2deb (0.24.2)
Hi Brian, thanks for the feedback and sorry for breaking your use case! The information you've provided isn't enough for me to reproduce the issue you describe (I've been trying for a while now :-) so I'm wondering:
py2deb -v ...
), capture the output and post it here? If you don't want to share the log output publicly on GitHub you can also e-mail it to me directly.Thanks in advance!
Have a same error for many packages =(
Expected requirement set to contain exactly one Python package whose name can be normalized to pylint-plugin-utils but encountered 0 packages instead
# pip3 list| grep py2deb
py2deb (1.1)
My requirements.txt contain this:
pylint
django==1.11
pylint-django
python-social-auth
django-notifications-hq
stripe
python-dateutil
analytics-python
django-allauth
bcrypt
python-magic
pytz
psycopg2
Pillow
https://github.com/celery/django-celery/archive/master.zip
celery==3.1.25
billiard==3.3.0.23
kombu==3.0.37
amqp==1.4.9
For reproduce it, you can use my script:
#!/bin/bash
for dep in `cat requirements.txt`
do
echo ''; echo ''
echo $dep
py2deb --name-prefix=python3 -r tmp/py2deb/ -- --no-deps $dep
#exit 0
done
with -- -r requirements.txt
work ok, but generate stupid unsolvable versions of dependencies.
Seems like people are still running into this and I myself ran into it again today, there's some issue with the logic on this line inside package.py
version = self.converter.transform_version(self, requirement.project_name, version)
I used the @trousev patch/hack and then everything worked fine
I'm reopening this and hopefully someone on the py2deb team can make a quick fix :)
So for a long time my python project had a setup.py with specific version of python packages.
Everything has worked fine for 6ish months and now suddenly I'm getting these errors: