Re: [pypy-dev] Visual Studio 2015 build strange behavior

ld be changed such that it it does not require additional efforts to investigate. Regards Sergey On Sat, Apr 8, 2017 at 10:36 PM, Sergey Kurdakov wrote: > Hi Matti, > >>Are you using 64-bit windows? Then using the editbin /largeaddressaware trick >>as mentioned on the windows bu

Re: [pypy-dev] Visual Studio 2015 build strange behavior

I did, but to no avail ( btw pypy builds with largeaddressaware flag too - so it is there either way ) so the memory error appears in spite of having /largeaddressaware trick, Regards Sergey On Sat, Apr 8, 2017 at 9:53 PM, Matti Picus wrote: > On 08/04/17 19:26, Sergey Kurdakov wrote: > >&

Re: [pypy-dev] Visual Studio 2015 build strange behavior

Hi Armin and Matti, now my project works. So concerning current stock installation of pypy seems that the only problem was a lack of sufficient stack space on windows, in debug pypy is configured to increase stack, but in release it is not. And as stack space is insufficient - some code might cr

Re: [pypy-dev] Visual Studio 2015 build strange behavior

Hi Armin, concerning pull request. there are few issues: the new PyVerify_fd code will not work with vs 2013 as that compiler has a bug: it reports console fd s as positive numbers ( earlier ms compilers and vs 2015 are correct to return negative values ) so both versions ( previous and new one

Re: [pypy-dev] Visual Studio 2015 build strange behavior

Apr 5, 2017 at 11:04 PM, Matti Picus wrote: > On 05/04/17 22:54, Sergey Kurdakov wrote: > >> Hi Armin, >> >> ok, I will prepare pull request, >> >> though there are other things to change. >> >> somehow openssl crashes on callback >> >> ope

Re: [pypy-dev] Visual Studio 2015 build strange behavior

( maybe I could just change that callback declaration to __cdecl) but maybe I just miss something, but I will look into issue, and when I'm fine with it I will make pull request then. Regards Sergey On Wed, Apr 5, 2017 at 10:08 PM, Armin Rigo wrote: > Hi Sergey, > > On 5 April 2017 at

Re: [pypy-dev] Visual Studio 2015 build strange behavior

WSAEWOULDBLOCK 10035L so all code logic checking real EWOULDBLOCK is misused by pypy compiled with VS 2015 now will try to play with that new definition, possibly code will start to make socket calls in VS 2015. Regards Sergey On Tue, Apr 4, 2017 at 8:43 AM, Sergey Kurdakov wrote

Re: [pypy-dev] Visual Studio 2015 build strange behavior

in VS2015 - will try that. Then will report of progress if I have some. Regards Sergey On Sun, Apr 2, 2017 at 11:03 AM, Armin Rigo wrote: > Hi Sergey, > > On 1 April 2017 at 13:57, Sergey Kurdakov wrote: > > but now I have seemingly more stable pypy, but at the same time th

[pypy-dev] Visual Studio 2015 build strange behavior

Hi, I managed to build pypy with visual studio 2015 ( win32 build on window 10/64 ) with both python and by pypy itself but I have one strange behavior it manifest in a first steps using new pypy by running pip pypy-c -mpip install -U wheel and an error reads Retrying (Retry(total=4, connect=

[pypy-dev] error building source pypy2-v5.7.0 cygwin 32/windows 64

Hi, as my windows pypy would always crash on my project but the same project on linux works fine and my main developing environment is windows I decided to try cygwin pypy so I got pypy2-v5.7.0-src.tar.bz2 and run on latest Cygwin-32 on windows 10/64 python ../../rpython/bin/rpython -Ojit target

Re: [pypy-dev] Django DateField default value and migrations fail

Hi All, after submitting a ticket a fix to Django is submitted by Django developer https://github.com/django/django/pull/7113 hope it will be in next Django release. Regards Sergey ___ pypy-dev mailing list pypy-dev@python.org https://mail.python.org

Re: [pypy-dev] Django DateField default value and migrations fail

Hi Yury, thanks for lambda tip, ok I will submit a ticket to Django, will see how it goes. Regards Sergey On Wed, Aug 17, 2016 at 12:53 PM, Yury V. Zaytsev wrote: > On Wed, 17 Aug 2016, Sergey Kurdakov wrote: > > class TestClass(models.Model): >> >> start_da

Re: [pypy-dev] Django DateField default value and migrations fail

tionType, wheras it's a types.MethodType on pypy. Maybe > that check could be expanded to include MethodType. > > Here's the code at master: > > https://github.com/django/django/blob/3b383085fb89a48e756383e7cd5d3b > d867353ba1/django/db/migrations/serializer.py#L3

Re: [pypy-dev] Django DateField default value and migrations fail

Hi William. I have created a test project ( just a new Django Project in PythonStudio so it is tested in Windows too, but this code will work on linux too ) http://ananas.ws/media/DjangoTest.zip unzip go to DjangoTest main directory and try to make migrations: DjangoTest>pypy manage.py makemigr

Re: [pypy-dev] Django DateField default value and migrations fail

e_deconstructed arg_string, arg_imports = cls.serialize(arg) File "/usr/local/lib/pypy2.7/dist-packages/django/db/migrations/writer.py", line 540, in serialize "topics/migrations/#migration-serializing" % (value, get_docs_version()) ValueError: Cannot serialize:

[pypy-dev] Django DateField default value and migrations fail

Hi All, there was a problem https://bitbucket.org/pypy/pypy/issues/2062/inconsistency-in-__repr__-for-date-time which caused Django not to make migrations https://code.djangoproject.com/ticket/24779 and the problem was fixed https://bitbucket.org/pypy/pypy/pull-requests/325/fixed-2062-treated-