Movatterモバイル変換

[0]ホーム
URL:

Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

 Sign up
Appearance settings

Reproducible PS/PDF output#6595

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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Closed
ghost wants to merge1 commit intomatplotlib:v2.xfromunknown repository
Closed

Reproducible PS/PDF output#6595

ghost wants to merge1 commit intomatplotlib:v2.xfromunknown repository

Conversation

ghost
Copy link

Several software packages use matplotlib in their building process (mainly to produce PS or PDF documents). To make their build reproducible, it would be great to make matplotlib output reproducible.

To allow reproducible PS and PDF output:

  • honour SOURCE_DATE_EPOCH for timestamps in PS and PDF files.
    Seehttps://reproducible-builds.org/specs/source-date-epoch/
  • get keys sorted so that hatch patterns, images and markers are included with
    a reproducible order in the PDF file. Another solution is to usesorted(six.iteritems(self.hatchPatterns)) inwriteHatches (and similar ordering inwriteImages andwriteMarkers), but this consumes more memory.

This patch has been submitted in debian bug#827361

See alsohttps://reproducible-builds.org/

To allow reproducible output:* honour SOURCE_DATE_EPOCH for timestamps in PS and PDF files.  Seehttps://reproducible-builds.org/specs/source-date-epoch/* get keys sorted so that hatchPatterns, images and markers are included with  a reproducible order in the PDF file.Seehttps://reproducible-builds.org/
@tacaswelltacaswell added this to the2.0.1 (next bug fix release) milestoneJun 16, 2016
@tacaswell
Copy link
Member

This may conflict with#6427 which is currently merged to master.

attn@jkseppan

@ghost
Copy link
Author

You're right I did not see that.#6427 corresponds to mysorted inpdfRepr. Should I adapt my patch and rebase to master?

@tacaswell
Copy link
Member

Yes please.

Thanks for being flexible about this.

On Thu, Jun 16, 2016 at 12:12 PM JojoBoulixnotifications@github.com
wrote:

You're right I did not see that.#6427
#6427 corresponds to my
sorted in pdfRepr. Should I adapt my patch and rebase to master?

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
#6595 (comment),
or mute the thread
https://github.com/notifications/unsubscribe/AAMMhftgvxO09-JkLaAA8AB0WIjvT7Dkks5qMXXRgaJpZM4I3Ulf
.

@ghostghost mentioned this pull requestJun 16, 2016
@ghost
Copy link
Author

I don't know how to do that in the same pull request so I created a new one:#6597.

@ghostghost closed thisJun 16, 2016
@tacaswell
Copy link
Member

Thanks. You can not re-direct a PR like that, opening a new one is the only option.

@QuLogicQuLogic modified the milestones:unassigned,2.0.1 (next bug fix release)Jun 17, 2016
This pull request wasclosed.
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

3 participants
@tacaswell@mdboom@QuLogic
[8]ページ先頭
©2009-2025 Movatter.jp