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

Finalize v0.37 deprecations #3602

Merged
merged 2 commits into from
Nov 16, 2022
Merged

Finalize v0.37 deprecations #3602

merged 2 commits into from
Nov 16, 2022

Conversation

banesullivan
Copy link
Member

This finalizes many deprecations that were targeted for v0.37 (which has already released). IMO, all of these are safe to remove at this point.

For any remaining deprecations, I made sure to add a note of planned removal; most targeting v0.40

@github-actions github-actions bot added the maintenance Low-impact maintenance activity label Nov 15, 2022
@codecov
Copy link

codecov bot commented Nov 15, 2022

Codecov Report

Merging #3602 (9749a11) into main (3d934e7) will decrease coverage by 0.04%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main    #3602      +/-   ##
==========================================
- Coverage   95.17%   95.13%   -0.05%     
==========================================
  Files          83       83              
  Lines       18579    18489      -90     
==========================================
- Hits        17683    17589      -94     
- Misses        896      900       +4     

Copy link
Member

@akaszynski akaszynski left a comment

Choose a reason for hiding this comment

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

LGTM. Thanks!

Copy link
Contributor

@MatthewFlamm MatthewFlamm left a comment

Choose a reason for hiding this comment

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

This should probably be merged after #3601, since that one targets main branch and this one removes the fixed code entirely.

Comment on lines -453 to -466
@property
def active_texture_name(self) -> Optional[str]: # pragma: no cover
"""Name of the active texture coordinates array.

.. deprecated:: 0.32.0
Use :attr:`DataSetAttributes.active_t_coords_name` to
return the name of the active texture coordinates array.

"""
warnings.warn(
"Use of `active_texture_name` is deprecated. Use `active_t_coords_name` instead.",
PyVistaDeprecationWarning,
)
return self.active_t_coords_name
Copy link
Member Author

Choose a reason for hiding this comment

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

I want to point out that is was not supposed to be deprecated... active_texture_name is not equivalent to active_t_coords_name. active_texture_name refers to a PyVista-specific feature I implemented a few years ago that tracks actual Texture objects so that if you have an "active texture" that add_mesh would pick up on it and render it automatically. This has no equivalent in VTK, so I'm fine with it now being broken/not supported, but we may want to clean all of this up in a new PR as the _textures property this is supposed to control still exists.

cc @pyvista/developers

@banesullivan banesullivan merged commit 2b0c0a9 into main Nov 16, 2022
@banesullivan banesullivan deleted the maint/deprecations branch November 16, 2022 03:28
@banesullivan banesullivan mentioned this pull request Feb 1, 2023
5 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
maintenance Low-impact maintenance activity
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants