question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

ImportError: The ``fake-factory`` package is now called ``Faker``.

See original GitHub issue

Trying to import factory, but it looks like since yesterday, one of the required packages has changed it’s name:

    import factory
  File "/venv/lib64/python3.5/site-packages/factory/__init__.py", line 46, in <module>
    from .faker import Faker
  File "/venv/lib64/python3.5/site-packages/factory/faker.py", line 41, in <module>
    import faker
  File "/venv/lib64/python3.5/site-packages/faker/__init__.py", line 7, in <module>
    raise ImportError(error)
ImportError: The ``fake-factory`` package is now called ``Faker``.

Edit: I now see there’s already a commit to fix this. Any chance of a release to pypi?

Issue Analytics

  • State:closed
  • Created 7 years ago
  • Reactions:46
  • Comments:14 (4 by maintainers)

github_iconTop GitHub Comments

15reactions
rbarroiscommented, Dec 17, 2016

Just fixed with 2.8.1 — I had to upload a couple of versions to fix an issue with recent setuptools versions.

Sorry for the release lag 😕

14reactions
bochechacommented, Dec 16, 2016

@jdufresne seems so, yes…

It broke our tests in Travis: https://travis-ci.org/ideascube/ideascube/builds/184587115

However, the same tests run just fine here in my pre-existing venv.

That’s because in my existing venv I have fake-factory==0.7.2 which satisfies the requirement on fake-factory>=0.5.0 from factory_boy (2.7.0).

But then when creating a new venv and installing factory_boy, then pip will download the latest version of fake-factory==9999.9.9, which only contains:

VERSION = '9999.9.9'

error = """The ``fake-factory`` package is now called ``Faker``.

Please update your requirements.
"""
raise ImportError(error

Nice.

Can we have a new release of factory_boy using Faker, please? 😃

Read more comments on GitHub >

github_iconTop Results From Across the Web

using python faker library but have import error - Stack Overflow
ImportError : The ``fake-factory`` package is now called ``Faker``. Please update your requirements. What am I missing here? python · importerror ...
Read more >
ImportError: The ``fake-factory`` package is now called ``Faker``.
Hi, we get this error with Python 3.4 and 3.5: https://travis-ci.org/urievenchen/speedy-net/jobs/185497863
Read more >
using python faker library but have import error - iTecNote
Python – using python faker library but have import error .libimporterrorpython ... ImportError: The ``fake-factory`` package is now called ``Faker``.
Read more >
FTBFS: ImportError: The ``fake-factory`` package is now called ...
Debian Bug report logs - #849388 factory-boy: FTBFS: ImportError: The ``fake-factory`` package is now called ``Faker``. version graph. Package: ...
Read more >
Developers - fake-factory update: Faker - - Bountysource
When trying to initiate the faker (via populator = Faker.getPopulator() ) it fails: ImportError: The ``fake-factory`` package is now called ``Faker``.
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found