[TIP] mocking a file in /proc

[David Palao]

Hi, James.
Thank you for your help. Yes something is wrong in my laptop. I tried
to install systemfixtures on the desktop and it works fine.
I guess this issue is OT anyway...

Best

2017-05-04 21:52 GMT+02:00 James Cooke <me at jamescooke.info>:
> Hi David,
>
> Something looks odd on your local machine. I've just installed locally
> with Python 3.5 (but not with clean pip cache) ... log attached in case
> it's helpful (I hope the server forwards attachments - if not I'll
> resend inline to you directly).
>
> Cheers,
>
> James
>
>
>
> On Thu, 4 May 2017, at 05:13 PM, David Palao 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
>
>
> --
> James Cooke
> Backend software developer
> CV PDF: http://jamescooke.info/docs/james_cooke_cv.pdf
> Website: http://jamescooke.info/
>
> _______________________________________________
> testing-in-python mailing list
> testing-in-python at lists.idyll.org
> http://lists.idyll.org/listinfo/testing-in-python
>