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

merge updated code #6

Merged
merged 16 commits into from Feb 19, 2019

Conversation

Projects
None yet
4 participants
@BenFields724
Copy link

commented Feb 19, 2019

takes in google updates and refreshed .exe

themonki and others added some commits May 11, 2017

Adding Google Transit Extension: platform_code
From reference of
https://developers.google.com/transit/gtfs/reference/gtfs-extensions#station-platforms

Field Name	Required	Details
platform_code	Optional	Indicates the platform identifier
				for a platform stop. This should be
				just the platform identifier (eg.
				"G" or "3"). Words like "platform"
				or "track" (or the feed’s
				language-specific equivalent) should
				not be included. This allows feed
				consumers to more easily
				internationalize and localize the
				platform identifier into other
				languages.
Fix excpetion style to be Python3 compatible
by running

    2to3 -nw -f except .

Part of google#412
change print statements to functions for Python compatibility
Another backwards compatible change as part of google#412

by running:

    futurize -nw -f libfuturize.fixes.fix_print_with_import  .
Merge pull request google#456 from jarondl/exceptions
Fix excpetion style to be Python3 compatible
Merge pull request google#431 from themonki/pr
Adding Google Transit Extension: platform_code
Switch to absolute imports for Python3 compatability
Part of google#412

Started by:
futurize -nw -f libfuturize.fixes.fix_absolute_import  .
And followed up by fixing a few local problems.
Solve some import dependency cycles that were exposed by absolute import
transitfeed has many import cycles, which is a bad thing. Converting
to absolute import exposed some of them. This changes adds the minimal
changes required to make imports work, for example by moving some
types from `problems.py` to `errors.py`.
More Python3/2 compatability changes
Part of google#412

Started with `futurize -nw --stage1 .`, but had to do a few manual
changes.
Merge pull request google#457 from jarondl/print
Change print statements to functions for Python compatibility
Merge pull request google#460 from jarondl/abs_import
 Switch to absolute imports for Python3 compatability
Merge pull request google#461 from jarondl/py3_misc
More Python3/2 compatability changes

@BenFields724 BenFields724 merged commit a640d7c into ODOT-PTS:master Feb 19, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.