-
-
Notifications
You must be signed in to change notification settings - Fork 95
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
merge_fixtures is having some problem parsing parameters with Python 3 #59
Comments
You need to add the following line in the merge_fixtures.py file:
You can see it in the latest commit on master, but it doesn't seem to have been updated on PyPi, unfortunately. |
i faced the same problem with django-fixture-magic installed from pypi. I guess that the Pypi-Version is not updated yet, because your commit did not update the version number. If you increase the version number in setup.py, PyPi might recognise, that there is an update. |
I added a similar add_arguments()-method to reorder_fixtures in Pull Request #61 |
@fuzzydolphin do @MaxBo's changes help? |
I experienced a similar issue as @fuzzydolphin while running |
A year later and this is still an issue I wonder why this is even closed |
I misread that it was fixed by #61. Reopening but it won’t be fixed unless someone’s got a PR for this. |
@davedash it's all about releasing what you have in master to pypi :) |
PyPI deploy steps have changed slightly - https://stackoverflow.com/questions/45207128/failed-to-upload-packages-to-pypi-410-gone |
The weird steps I remembered from the last time I did this worked :)
https://pypi.org/project/django-fixture-magic/
I really outta put this in Travis
Dave Dash
…On Fri, Oct 19, 2018 at 11:01 AM Sean Chon ***@***.***> wrote:
PyPI deploy steps have changed slightly -
https://stackoverflow.com/questions/45207128/failed-to-upload-packages-to-pypi-410-gone
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#59 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AADoaTCf02Tp9a2vhRC9iSxA58_sdOTdks5umhKggaJpZM4Ph8HN>
.
|
Just ran into this error, confirmed it's fixed by using master:
|
I also confirmed that the source files from PyPi do not match the ones on github master. PyPi still contains the old buggy copy of I did a diff of the PyPi package's
As a workaround, I would need to package the correct copy on an internal devpi server myself, because unfortunately I cannot use github in the environment I am working on. |
@mghantous Can you let me know if https://pypi.org/project/django-fixture-magic/0.1.5/ fixes things? This is from master. |
Hi @davedash you made me realize that I was actually on
I'm using python 3.6 and django 2.2. Thanks. |
@davedash I think I may have identified the problem. If you navigate here you will see there is no https://pypi.org/simple/django-fixture-magic/ I read in one article that you may need to do |
I uploaded a wheel version and tried locally to verify that it now works.
DOes this work for you?
Dave Dash
…On Wed, Jul 15, 2020 at 12:14 PM Matthew Ghantous ***@***.***> wrote:
@davedash <https://github.com/davedash> I think I may have identified the
problem. If you navigate here you will see there is no 0.1.4 or 0.1.5
(but there is a version called 0.1.4.macosx-10.13-x86_64).
https://pypi.org/simple/django-fixture-magic/
I read in one article that you may need to do python setup.py bdist_wheel
upload to get it to show up there.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#59 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAAOQ2O4SKAQAI76YBHMKEDR3X5X3ANCNFSM4D4HYHGQ>
.
|
Yes. And it appears I am pretty sure this issue can be closed now. |
Using the following Python and Django
Python 3.4.6
Django 1.10.7
When I run the merge_fixtures command
It shows the following error message:
I looked into it a little bit and it seems to be unhappy in parsing the command line parameters. I think it is unhappy here:
But I am a bit unfamiliar with what is expected here and didn't have time to fully investigate the issue. Do you have a hint where I should be looking?
The text was updated successfully, but these errors were encountered: