Skip to content
This repository was archived by the owner on May 23, 2023. It is now read-only.

Conversation

@pipermerriam
Copy link
Member

Fix the VM issues and some other bytes/str/int/long py2/3 related bugs.

leaves-6c86c4bf1de24fb4822f97a7b86a8830

pipermerriam referenced this pull request Jun 23, 2016
@pipermerriam pipermerriam force-pushed the piper/fix-block-tests-invalid-state branch from f374476 to b06829e Compare June 24, 2016 16:59
@pipermerriam
Copy link
Member Author

@vbuterin this PR fixes some python3 errors that have been introduced in some of your recent work implementing the various EIP proposals.

@konradkonrad konradkonrad mentioned this pull request Jun 28, 2016
15 tasks
@pipermerriam pipermerriam force-pushed the piper/fix-block-tests-invalid-state branch from b06829e to fd0a4ff Compare June 28, 2016 18:22
trie_root = Binary.fixed_length(32, allow_empty=True)


class bcolors:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why did you remove this?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It is only used by the slogging module so I moved it over to there. Happy to move it back if it's a problem.

@konradkonrad
Copy link
Contributor

This looks okay to me -- in general I think I prefer PR's that stay inside their scope, i.e. fixing py3 things should not try to refactor the package structure, too. (Not that I haven't broken that rule myself in the past ;) )

@konradkonrad konradkonrad merged commit 4e1f64f into ethereum:develop Jun 29, 2016
@pipermerriam
Copy link
Member Author

I completely agree with keeping pull requests contained to single things. I
feel like this specific refactor was somehow related but I'm struggling to
recall how. Maybe relative imports?

Either way I'll do better keeping unrelated things separate

On Wed, Jun 29, 2016, 9:05 AM konradkonrad notifications@github.com wrote:

This looks okay to me -- in general I think I prefer PR's that stay inside
their scope, i.e. fixing py3 things should not try to refactor the package
structure, too. (Not that I haven't broken that rule myself in the past ;) )


You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
#369 (comment),
or mute the thread
https://github.com/notifications/unsubscribe/AAyTgqaL_gVyCW8f2HcdejUTqGb5vLQSks5qQomvgaJpZM4I9VOU
.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants