-
Notifications
You must be signed in to change notification settings - Fork 246
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
OverflowError: Python int too large to convert to C long #41
Comments
some more investigation:
need to check the how slices are sent with brine... something's fishy. |
Client Coed
Server Side
Client Side
|
FUUUUUUUUUUUUUUUUUUUUUUUUUU. it's taken me a while to realize that
what i have so far is this: when you write
python sucks. i'll try to find a way to overcome this, but i don't suppose it would be easy.
|
Yaniv Aknin:
|
While it's adding a hack to a patch, I wanted to also say that RPyC can check whether someone override If |
@yaniv-aknin: |
Good question, I was thinking only about user classes that don't have a native First, I think my suggestion still stands in that case. Second, specifically for |
no, this is very ugly and unlikely to be worth the effort and possible bugs. and it's a slippery slope... do it here and you'll find a dozen other places. i'm not going to invite an avalanche in. |
There have been precedents of similar ugliness in the virtualization world (paravirtualization/dynamic instruction translation), but at the end of the day, it's up to you. Personally I don't think it's /that/ much of an important feature. |
okay, here's what i'll do:
i think it's safe to assume how can i be so sure? |
Makes perfect sense. Special cases aren't special enough to break the rules
On Sun, Jun 5, 2011 at 1:18 PM, tomerfiliba <
|
re-closed 95bc275 |
reported by rudiger. here's a code snippet to reproduce the problem:
very weird.
The text was updated successfully, but these errors were encountered: