Skip to content
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

some fixes to python example scripts for python3 compatibility #415

Merged
merged 3 commits into from
Oct 16, 2018

Conversation

c-holtermann
Copy link
Contributor

No description provided.

@@ -126,7 +126,7 @@ def period_end(start_year, start_month, period_type):
# so we get a period end like
# 2010-03-31 for period starting 2010-01 instead of 2010-04-01
return date(end_year, end_month, 1) - ONE_DAY


def generate_period_boundaries(start_year, start_month, period_type, periods):
for i in xrange(periods):
Copy link
Contributor

Choose a reason for hiding this comment

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

Shouldn't xrange be changed to range?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Good point. I'm sure there are some more things like this.

thanks to Sumit Bhardwaj for the hint
@c-holtermann
Copy link
Contributor Author

c-holtermann commented Sep 22, 2018

I've created a bug report as a collection for remaining issues in the transition from python 2 to python 3.
https://bugs.gnucash.org/show_bug.cgi?id=796863

@jralls
Copy link
Member

jralls commented Sep 24, 2018

Do you want to keep working on this PR until Friday (when I start putting the release together) or make a new one for more changes?

@c-holtermann
Copy link
Contributor Author

Let's keep this one till friday.

@code-gnucash-org code-gnucash-org merged commit 64a28b5 into Gnucash:maint Oct 16, 2018
@jralls
Copy link
Member

jralls commented Oct 16, 2018

Well, that Friday came and went along with the release of 3.3, so this missed it. I've merged now to keep that from happening again. You'll just have to make a new PR when you get around to working on this again.

Thanks.

@c-holtermann
Copy link
Contributor Author

Thanks. I was busy with some other projects but will pick this up again the coming weeks. Good to be reminded.

@c-holtermann
Copy link
Contributor Author

Until the next release things about python3 should be fixed (that's my goal). I saw this PR as part of that and didn't feel a need to hurry.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants