8000 Datetime failures with MinGW (Trac #2108) · Issue #5904 · thouis/numpy-trac-migration · GitHub
[go: up one dir, main page]
Skip to content
8000

Datetime failures with MinGW (Trac #2108) #5904

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.

Sign up for GitHub

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

Jump to bottom
Open
numpy-gitbot opened this issue Oct 16, 2012 · 1 comment
Open

Datetime failures with MinGW (Trac #2108) #5904

numpy-gitbot opened this issue Oct 16, 2012 · 1 comment
Labels
component: numpy.core Defect priority: normal
Milestone
NumPy 1.7

Comments

@numpy-gitbot
Copy link
Collaborator

Original ticket http://projects.scipy.org/numpy/ticket/2108 on 2012-04-16 by atmention:rgommers, assigned to unknown.

See numpy/numpy#214

These failures are hard to fix for MinGW 3.4.5. Until we can do everything with MinGW 4.x (including distributing binaries) we do have a problem.
@numpy-gitbot
Copy link
Collaborator Author

atmention:rgommers wrote on 2012-04-16

It's not yet clear to me how much of datetime would be unusable on Windows if we would do a release right now. Can anyone comment on that? If it's a major part, then I think this is a blocker. If it's a minor issue, then we may decide to ignore it (there's an experimental label for a reason).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
component: numpy.core Defect priority: normal
Projects
None yet
Milestone
NumPy 1.7
Development

No branches or pull requests
1 participant
@numpy-gitbot
0