[TIP] mocking a file in /proc

[David Palao]

Hi again,
Ok, after some cleaning-up in my system, I get systemfixtures
installed in Python-3.5 and Python-3.6 venvs. Python-3.4 still
complains (same error). But it is not critical for now...
I'm eager now to test the package, finally!
Thanks again.

Best


2017-05-05 9:59 GMT+02:00 David Palao <dpalao.python at gmail.com>:
> Hi, Robert.
> Thank you for your comment.
> Not sure about the python2 part though. I had a look at the pip
> executable that is called and it looks ok.
>
> I think pip has definitely something to do: I had other issues
> regarding encoding after upgrading pip. Maybe there is some locale
> inconsistency in my system...
>
> But as I said before, this problem is OT.
>
> Best
>
>
>
> 2017-05-04 22:47 GMT+02:00 Robert Collins <robertc at robertcollins.net>:
>> I'm 99%sure that pip there is being run by a Python 2.x interpreter.
>>
>> On 5 May 2017 4:13 am, "David Palao" <dpalao.python at gmail.com> wrote:
>>>
>>> Hi,
>>> Sorry for the looong delay. I had to interrupt the development for a
>>> while...
>>>
>>> Anyway, thank you for the comments and suggestions.
>>>
>>> I'm trying to install systemfixtures, as it looks interesting. But I get:
>>> $ pip install systemfixtures
>>> Collecting systemfixtures
>>>   Using cached systemfixtures-0.6.5-py2.py3-none-any.whl
>>> Collecting requests-mock (from systemfixtures)
>>>   Downloading requests_mock-1.3.0-py2.py3-none-any.whl
>>> Collecting subprocess32; python_version < "3.5" (from systemfixtures)
>>>   Using cached subprocess32-3.2.7.tar.gz
>>>     Complete output from command python setup.py egg_info:
>>>     This backport is for Python 2.x only.
>>>
>>>     ----------------------------------------
>>> Command "python setup.py egg_info" failed with error code 1 in
>>> /tmp/pip-build-7lg20nsr/subprocess32
>>>
>>> Do you understand it?
>>> I'm using python-3.5 (but I tried with 3.4 and 3.6 as well).
>>> Should I open an issue in systemfixtures?
>>>
>>> Thanks in advance!
>>>
>>> 2017-01-24 15:58 GMT+01:00 Free Ekanayaka <free at ekanayaka.io>:
>>> > James Cooke <me at jamescooke.info> writes:
>>> >
>>> >> Hello,
>>> >>
>>> >>
>>> >>
>>> >> My suggestion is that you checkout pyfakefs:
>>> >> https://github.com/jmcgeheeiv/pyfakefs |
>>> >> https://pypi.python.org/pypi/pyfakefs
>>> >
>>> > I didn't know about pyfakes.
>>> >
>>> > FWIW systemfixtures seem to do the same:
>>> >
>>> > http://systemfixtures.readthedocs.io/en/latest/#filesystem
>>> > https://github.com/testing-cabal/systemfixtures
>>> >
>>> > The main differences I could see are:
>>> >
>>> > 1) systemfixtures uses composition instead of inheritance, i.e. you
>>> >    can call self.useFixture(FakeFilesystem()) instead of inheriting
>>> >    from fake_filesystem_unittest.TestCase and calling
>>> >    self.setUpPyfakefs()
>>> >
>>> > 2) there's no dependency on Python mock
>>> >
>>> > Free
>>> >
>>> > _______________________________________________
>>> > testing-in-python mailing list
>>> > testing-in-python at lists.idyll.org
>>> > http://lists.idyll.org/listinfo/testing-in-python
>>>
>>> _______________________________________________
>>> testing-in-python mailing list
>>> testing-in-python at lists.idyll.org
>>> http://lists.idyll.org/listinfo/testing-in-python