If you are not sure if the website you would like to visit is secure, you can verify it here. Enter the website address of the page and see parts of its content and the thumbnail images on this site. None (if any) dangerous scripts on the referenced page will be executed. Additionally, if the selected site contains subpages, you can verify it (review) in batches containing 5 pages.
favicon.ico: github.com/JoshData/python-email-validator/pull/65 - More Structured Errors? by els.

site address: github.com/JoshData/python-email-validator/pull/65 redirected to: github.com/JoshData/python-email-validator/pull/65

site title: More Structured Errors? by elsiehupp · Pull Request #65 · JoshData/python-email-validator · GitHub

Our opinion (on Tuesday 17 November 2026 17:31:38 UTC):

GREEN status (no comments) - no comments
After content analysis of this website we propose the following hashtags:



Meta tags:
description=A robust email syntax and deliverability validation library for Python. - More Structured Errors? by elsiehupp · Pull Request #65 · JoshData/python-email-validator;

Headings (most frequently used words):

uh, oh, commented, sep, 2021, elsiehupp, more, structured, navigation, 11, 12, errors, to, python, email, validator, footer, joshdata, 65, menu, repository, 65elsiehupp, wants, merge, commit, intojoshdata, mainjoshdata, mainfrom, errorselsiehupp, errorscopy, head, branch, name, clipboard, conversation, problem, scope, possible, solutions, miscellaneous, comments, reviewers, assignees, labels, projects, milestone, development, participants,

Text of the page (most frequently used words):
the (76), this (39), error (33), and (25), that (24), response (21), copy (20), code (18), thing (18), #elsiehupp (17), there (16), for (15), github (14), while (14), from (14), reload (14), more (14), something (14), err (14), was (13), joshdata (13), all (13), please (12), existing (12), with (12), errors (12), python (12), applied (11), loading (11), page (11), 2021 (11), email (11), you (9), can (9), main (9), sorry (9), went (9), wrong (9), reactions (9), markdown (9), link (9), commented (9), sep (9), catch (9), structured (9), validator (9), cannot (8), pull (8), branch (8), tests (8), test (8), classes (8), string (8), into (8), not (7), suggestion (7), suggestions (7), request (7), have (7), sign (7), like (7), message (7), strings (7), your (7), messages (7), could (7), new (7), compare (6), force (6), pushed (6), just (6), author (6), out (6), would (6), localization (6), are (6), approach (6), subclasses (6), security (5), way (5), parsing (5), how (5), content (5), support (5), information (4), order (4), commit (4), one (4), may (4), what (4), about (4), times (4), most (4), recently (4), draft (4), but (4), which (4), coverage (4), complicated (4), application (4), custom (4), errortypea (4), try (4), build (4), failure (4), copilot (4), navigation (3), now (3), merge (3), line (3), add (3), batch (3), projects (3), conversation (3), hidden (3), characters (3), unicode (3), learn (3), september (3), 2023 (3), mail (3), box (3), anyway (3), typically (3), implemented (3), dynamic (3), make (3), them (3), easier (3), work (3), does (3), downstream (3), possible (3), return (3), errortypeb (3), do_check (3), alternate (3), probably (3), part (3), class (3), script (3), signed (3), testing (3), their (3), own (3), documentation (3), quality (3), another (3), tab (3), window (3), refresh (3), session (3), developers (3), changelog (3), customer (3), enterprise (3), grade (3), features (3), community (2), status (2), footer (2), 2026 (2), right (2), check (2), comments (2), reviews (2), marked (2), must (2), create (2), single (2), only (2), per (2), changes (2), issues (2), development (2), milestone (2), none (2), yet (2), already (2), account (2), comment (2), file (2), bidirectional (2), than (2), review (2), isn (2), done (2), too (2), next (2), here (2), fleshing (2), unit (2), don (2), checks (2), know (2), well (2), building (2), need (2), understand (2), completely (2), creating (2), zillion (2), question (2), far (2), get (2), copying (2), hard (2), coded (2), some (2), owner (2), example (2), lot (2), function (2), might (2), other (2), parameters (2), client (2), subclass (2), give (2), error_message_a1 (2), complexity (2), either (2), lots (2), finally (2), param4 (2), param3 (2), param2 (2), param1 (2), difficult (2), messy (2), address (2), localized (2), case (2), rather (2), keys (2), table (2), thanks (2), project (2), assert (2), isinstance (2), false (2), emaildomainstartswithperioderror (2), any (2), running (2), 7799902 (2), alert (2), see (2), problem (2), scope (2), break (2), cases (2), raised (2), solution (2), number (2), based (2), mode (2), wants (2), head (2), name (2), clipboard (2), insights (2), actions (2), repository (2), universe (2), training (2), integrations (2), stories (2), center (2), business (2), fixes (2), products (2), secret (2), perform, action, time, share, personal, manage, cookies, contact, docs, privacy, terms, inc, back, later, queued, multi, pending, has, been, resolved, outdated, change, valid, applying, deleted, lines, supported, viewing, subset, closed, invalid, because, were, made, participants, successfully, merging, close, these, labels, assigned, assignees, reviewers, join, free, show, contains, text, interpreted, compiled, differently, appears, below, open, editor, reveals, november, 603b955, 1bfe6b7, dbf4618, 0df8b7a, april, f18da74, 5c9973d, march, d6a5d4b, 1c0390b, 2022, 95deaf8, ffe1669, marking, emphasize, immediate, priority, yeah, had, feeling, regardless, think, step, going, cover, contribute, specifically, mentions, welcome, contribution, practice, checking, exactly, matches, hence, means, many, separate, static, those, before, fwiw, didn, fact, constructed, variables, call, actually, __str__, thought, start, improving, then, distinction, sense, basically, adding, little, bit, library, dramatically, simplifies, enumerating, without, breaking, depends, even, implement, both, first, two, options, simultaneously, applications, flexibility, versus, current, error_message_b_other, error_message_b4, error_message_b3, error_message_b2, error_message_b1, error_message_a_other, error_message_a4, error_message_a3, error_message_a2, error_message_e, errortypee, error_message_d, errortyped, error_message_c, errortypec, error_message_b, error_message_a, say, issue, depending, cleaner, pass, closer, original, format, necessary, exception, period, immediately, after, overly, handled, mapping, codes, tables, structure, needed, except, variable, substitutions, within, considered, stable, lookup, replaced, yep, started, exc_info, error_class, assertionerror, where, exceptioninfo, tblen, email_validator, error_classes, idea, fix, okay, looks, broken, wasn, correctly, computer, a2bb69d, off, elsie, hupp, 9206310, users, noreply, com, spoiler, related, maintainer, over, mailinabox, 2028, thoughts, resolving, initial, seem, better, direction, should, instead, feedback, continuing, polish, duplicates, whole, bunch, reimplement, avoid, duplication, wanted, leave, initially, unchanged, demonstrate, imported, individually, big, long, list, visualize, covered, considering, roughly, clear, pretty, thin, validate_email, added, least, works, pulled, submodule, find, read, descriptions, prove, unnecessary, alternative, extracted, wherever, they, remained, child, replacing, under, scenario, someone, miscellaneous, involve, named, reason, hesitant, take, route, enough, concerned, involved, target, granted, almost, certainly, superior, tried, large, sub, trick, guess, though, uneasy, resulting, being, somewhat, excessive, solutions, detailed, contextual, validation, available, define, parse, brittle, contributing, uses, difficulty, triggering, possibly, input, files, changed, commits, items, wiki, requests, dismiss, switched, accounts, appearance, settings, search, pricing, event, talks, workshops, partners, company, forum, events, webinars, blog, resource, connect, resources, premium, advanced, ons, trust, why, evaluate, industries, government, manufacturing, financial, services, healthcare, industry, nonprofits, startups, team, enterprises, stage, businesses, source, latest, improvements, across, place, developer, articles, sponsors, trending, repos, explore, customize, certifications, scanning, leak, prevention, protection, vulnerability, detection, remediation, secure, cloud, environments, codespaces, analysis, enforcement, automation, ship, coding, agent, tasks, automated, hosting, collaboration, platform, menu, skip,


Text of the page (random words):
more structured errors by elsiehupp pull request 65 joshdata python email validator github skip to content navigation menu sign in products platform github repository hosting code review and collaboration copilot ai coding agent for tasks projects and automated work build ship actions ci cd and automation code quality quality analysis fixes and enforcement codespaces cloud development environments secure code security vulnerability detection and remediation secret protection secret scanning and leak prevention all features developers learn documentation training certifications build build with copilot customize copilot integrations explore trending repos github sponsors developer articles changelog changelog your source for the latest features improvements and fixes across github products all in one place businesses by stage enterprises team startups nonprofits by industry healthcare financial services manufacturing government see all industries evaluate github why github customer stories business insights trust center add ons github advanced security enterprise grade code security copilot for business enterprise grade ai features premium support enterprise grade 24 7 support resources learn connect documentation resource center blog events webinars community forum customer stories integrations support customer support training github status company about partners changelog github universe github universe the event for developers by developers talks workshops and what s next for github pricing search sign in sign up appearance settings you signed in with another tab or window reload to refresh your session you signed out in another tab or window reload to refresh your session you switched accounts on another tab or window reload to refresh your session dismiss alert message joshdata python email validator repository navigation code issues 12 12 pull requests 5 5 actions projects wiki security and quality insights more items more structured errors 65 65 draft elsiehupp wants to merge 1 commit into joshdata main joshdata python email validator main from elsiehupp more structured errors elsiehupp python email validator more structured errors copy head branch name to clipboard conversation commits 1 1 checks files changed draft more structured errors 65 elsiehupp wants to merge 1 commit into joshdata main joshdata python email validator main from elsiehupp more structured errors elsiehupp python email validator more structured errors copy head branch name to clipboard conversation elsiehupp commented sep 6 2021 copy link copy markdown problem scope i am contributing to a project that uses python email validator and a difficulty i m running into is triggering custom and possibly localized error messages in my own downstream code based on an input email address s failure mode right now the more detailed contextual information for a validation failure is only available as part of the message string of the error raised in order to define my own error messages based on the failure mode i would need to parse the message string which is brittle and messy possible solutions the solution i tried here is to create a large number of sub classes of python email validator s existing custom error classes this does the trick i guess though i m uneasy about the resulting number of error classes being somewhat excessive an alternate solution could involve fleshing out python email validator s existing custom error classes with named parameters and the like the reason i m hesitant to take this route is that i m new enough to python that i m concerned the complexity involved might be difficult to target to python 2 7 granted this is almost certainly the superior approach miscellaneous comments wherever i raised the new error subclasses they remained child classes of the error class i was replacing this way under the possible scenario that someone was already testing for error classes the new subclasses would not break their code i pulled the error subclasses out into their own submodule so that it s easier to find them and read their descriptions this may prove unnecessary with an alternative approach and a lot of the new information could be extracted into the documentation i added the new error subclasses to the test script and at least with python 3 testing for errors by class works as well as testing errors by message string i imported the new error subclasses to the test script individually in a big long list rather than with a in part in order to make it easier to visualize which cases from validate_email are covered by the tests considering there s roughly one error subclass per failure case it s clear that the existing tests have pretty thin coverage of the existing cases the way i implemented the tests duplicates a whole bunch of the existing test code i could probably reimplement the tests so as to avoid this code duplication but i wanted to leave the existing tests initially unchanged in order to demonstrate that the new subclasses don t break the existing tests anyway what are your thoughts on resolving this problem scope does this initial approach seem like the better direction or should i try the alternate approach instead and do you have any other feedback i can work with in continuing to polish this pull request thanks sorry something went wrong uh oh there was an error while loading please reload this page all reactions elsiehupp commented sep 6 2021 copy link copy markdown author spoiler alert this is related to mail in a box mailinabox 2028 as i see you re the maintainer over there too all reactions sorry something went wrong uh oh there was an error while loading please reload this page more structured errors 7799902 signed off by elsie hupp 9206310 elsiehupp users noreply github com elsiehupp force pushed the more structured errors branch from a2bb69d to 7799902 compare september 6 2021 23 35 elsiehupp commented sep 6 2021 copy link copy markdown author okay it looks like my test code is broken i probably wasn t running the test script correctly on my computer any idea how to fix this assert isinstance exc_info error_class e assertionerror assert false e where false isinstance exceptioninfo emaildomainstartswithperioderror tblen 3 class email_validator error_classes emaildomainstartswithperioderror all reactions sorry something went wrong uh oh there was an error while loading please reload this page joshdata commented sep 11 2021 copy link copy markdown owner hi thanks yep i started this project in part to support mail in a box this is probably overly complicated if this is just about localization typically localization is handled by mapping strings or id codes for error messages to tables of localized strings in that case structure isn t needed except for error messages that have variable substitutions within them rather the error message strings are either considered stable keys for lookup into a localization table or the strings are replaced with keys and we build in a localization table how far can you get by just copying the hard coded error message strings e g an email address cannot have a period immediately after the sign into your application to check which error the exception is all reactions sorry something went wrong uh oh there was an error while loading please reload this page elsiehupp commented sep 11 2021 copy link copy markdown author i would say the issue with depending on strings is that parsing code is difficult and messy and it s cleaner to pass information in closer to the original format if necessary so for example downstream code could be something like try response do_check thing catch errortypea response error_message_a thing catch errortypeb response error_message_b thing catch errortypec response error_message_c thing catch errortyped response error_message_d thing catch errortypee response error_message_e thing return response the alternate approach would be something like try response do_check thing catch errortypea as err if err param1 response error_message_a1 thing if err param2 response error_message_a2 thing if err param3 response error_message_a3 thing if err param4 response error_message_a4 thing finally response error_message_a_other thing catch errortypeb as err if err param1 response error_message_b1 thing if err param2 response error_message_b2 thing if err param3 response error_message_b3 thing if err param4 response error_message_b4 thing finally response error_message_b_other thing return response versus the current approach try response do_check thing catch errortypea as err lots of complicated string parsing catch errortypeb as err lots of complicated string parsing return response does this distinction make sense basically adding a little bit of complexity in this library dramatically simplifies enumerating the errors in a downstream application either way it can be done without breaking existing code that depends on string parsing and it would even be possible to implement both the first two options simultaneously just to give client applications more flexibility anyway my thought is that i could start by improving the test coverage and then i could go from there all reactions sorry something went wrong uh oh there was an error while loading please reload this page elsiehupp commented sep 11 2021 copy link copy markdown author fwiw the example code in my comment just now didn t account for the fact that a lot of the existing error messages are constructed from variables so a function call like error_message_a1 err might actually do something with other parameters from err or a client application could subclass errortypea and give it a custom __str__ function all reactions sorry something went wrong uh oh there was an error while loading please reload this page joshdata commented sep 12 2021 copy link copy markdown owner i understand completely but creating a zillion error classes is not the way localization is typically implemented checking if a string exactly matches there must be something before the sign is not complicated string parsing hence my question how far can you get by just copying the hard coded error message strings into your application i know that there are some messages that have some dynamic content so what my question means is how many have dynamic content how can we separate the dynamic content from the static content of those messages to make them easier to work with all reactions sorry something went wrong uh oh there was an error while loading please reload this page elsiehupp commented sep 12 2021 copy link copy markdown author i understand completely but creating a zillion error classes is not the way localization is typically implemented yeah i had that feeling too but regardless i think my next step here is going to be fleshing out the unit tests for the existing code the existing unit tests don t cover all of the checks i know that mail in a box which i would like to contribute to as well specifically mentions building out test coverage as a welcome contribution and building out test coverage is something i need more practice with anyway all reactions sorry something went wrong uh oh there was an error while loading please reload this page elsiehupp marked this pull request as draft september 12 2021 22 59 elsiehupp commented sep 12 2021 copy link copy markdown author i m marking this as a draft just to emphasize that it isn t done and that the code in this pull request is not my immediate priority all reactions sorry something went wrong uh oh there was an error while loading please reload this page joshdata force pushed the main branch 5 times most recently from ffe1669 to 95deaf8 compare may 1 2022 22 18 joshdata force pushed the main branch 3 times most recently from 1c0390b to d6a5d4b compare march 1 2023 23 31 joshdata force pushed the main branch 3 times most recently from 5c9973d to f18da74 compare april 16 2023 01 19 joshdata force pushed the main branch 2 times most recently from 0df8b7a to dbf4618 compare september 26 2023 11 24 joshdata force pushed the main branch from 1bfe6b7 to 603b955 compare november 7 2026 16 55 this file contains hidden or bidirectional unicode text that may be interpreted or compiled differently than what appears below to review open the file in an editor that reveals hidden unicode characters learn more about bidirectional unicode characters show hidden characters sign up for free to join this conversation on github already have an account sign in to comment reviewers no reviews uh oh there was an error while loading please reload this page assignees no one assigned labels none yet projects none yet milestone no milestone development successfully merging this pull request may close these issues uh oh there was an error while loading please reload this page 2 participants add this suggestion to a batch that can be applied as a single commit this suggestion is invalid because no changes were made to the code suggestions cannot be applied while the pull request is closed suggestions cannot be applied while viewing a subset of changes only one suggestion per line can be applied in a batch add this suggestion to a batch that can be applied as a single commit applying suggestions on deleted lines is not supported you must change the existing code in this line in order to create a valid suggestion outdated suggestions cannot be applied this suggestion has been applied or marked resolved suggestions cannot be applied from pending reviews suggestions cannot be applied on multi line comments suggestions cannot be applied while the pull request is queued to merge suggestion cannot be applied right now please check back later footer 2026 github inc footer navigation terms privacy security status community docs contact manage cookies do not share my personal information you can t perform that action at this time
Thumbnail images (randomly selected): * Images may be subject to copyright.GREEN status (no comments)
  • @elsiehupp
  • @elsiehupp
  • @elsiehupp
  • @elsiehupp
  • @elsiehupp
  • @JoshData
  • @JoshData
  • @elsiehupp
  • @JoshData

Verified site has: 76 subpage(s). Do you want to verify them? Verify pages:

1-5 6-10 11-15 16-20 21-25 26-30 31-35 36-40 41-45 46-50
51-55 56-60 61-65 66-70 71-75 76-76


Top 50 hastags from of all verified websites.

Supplementary Information (add-on for SEO geeks)*- See more on header.verify-www.com

Header

HTTP/1.1 301 Moved Permanently
Content-Length 0
Location htt????/github.com/JoshData/python-email-validator/pull/65
connection close
HTTP/2 200
date Tue, 17 Nov 2026 17:31:38 GMT
content-type text/html; charset=utf-8
cache-control no-cache
content-security-policy default-src none ; base-uri self ; child-src github.githubassets.com github.com/assets-cdn/worker/ github.com/assets/ gist.github.com/assets-cdn/worker/; connect-src self uploads.github.com www.githubstatus.com collector.github.com raw.githubusercontent.com api.github.com github-cloud.s3.amazonaws.com github-production-repository-file-5c1aeb.s3.amazonaws.com github-production-upload-manifest-file-7fdce7.s3.amazonaws.com github-production-user-asset-6210df.s3.amazonaws.com *.rel.tunnels.api.visualstudio.com wss://*.rel.tunnels.api.visualstudio.com github.githubassets.com objects-origin.githubusercontent.com copilot-proxy.githubusercontent.com proxy.individual.githubcopilot.com proxy.business.githubcopilot.com proxy.enterprise.githubcopilot.com *.actions.githubusercontent.com wss://*.actions.githubusercontent.com productionresultssa0.blob.core.windows.net productionresultssa1.blob.core.windows.net productionresultssa2.blob.core.windows.net productionresultssa3.blob.core.windows.net productionresultssa4.blob.core.windows.net productionresultssa5.blob.core.windows.net productionresultssa6.blob.core.windows.net productionresultssa7.blob.core.windows.net productionresultssa8.blob.core.windows.net productionresultssa9.blob.core.windows.net productionresultssa10.blob.core.windows.net productionresultssa11.blob.core.windows.net productionresultssa12.blob.core.windows.net productionresultssa13.blob.core.windows.net productionresultssa14.blob.core.windows.net productionresultssa15.blob.core.windows.net productionresultssa16.blob.core.windows.net productionresultssa17.blob.core.windows.net productionresultssa18.blob.core.windows.net productionresultssa19.blob.core.windows.net productionresultssa30.blob.core.windows.net productionresultssa31.blob.core.windows.net productionresultssa32.blob.core.windows.net github-production-repository-image-32fea6.s3.amazonaws.com github-production-release-asset-2e65be.s3.amazonaws.com insights.github.com wss://alive.github.com wss://alive-staging.github.com api.githubcopilot.com api.individual.githubcopilot.com api.business.githubcopilot.com api.enterprise.githubcopilot.com wss://production-copilot-host.webpubsub.azure.com wss://production-copilot-host-centralus.webpubsub.azure.com wss://production-copilot-host-centralus-02.webpubsub.azure.com wss://production-copilot-host-westus.webpubsub.azure.com wss://production-copilot-host-westus3.webpubsub.azure.com wss://production-copilot-host-eastasia.webpubsub.azure.com wss://production-copilot-host-austriaeast.webpubsub.azure.com api.github.com/cmc_internal/api/; font-src github.githubassets.com; form-action self github.com gist.github.com copilot-workspace.githubnext.com objects-origin.githubusercontent.com; frame-ancestors none ; frame-src viewscreen.githubusercontent.com notebooks.githubusercontent.com; img-src self data: blob: github.githubassets.com media.githubusercontent.com camo.githubusercontent.com identicons.github.com avatars.githubusercontent.com private-avatars.githubusercontent.com github-cloud.s3.amazonaws.com objects.githubusercontent.com release-assets.githubusercontent.com secured-user-images.githubusercontent.com user-images.githubusercontent.com private-user-images.githubusercontent.com opengraph.githubassets.com repository-images.githubusercontent.com marketplace-screenshots.githubusercontent.com copilotprodattachments.blob.core.windows.net/github-production-copilot-attachments/ github-production-user-asset-6210df.s3.amazonaws.com customer-stories-feed.github.com spotlights-feed.github.com explore-feed.github.com *.googleusercontent.com objects-origin.githubusercontent.com *.githubusercontent.com; manifest-src self ; media-src github.com user-images.githubusercontent.com secured-user-images.githubusercontent.com private-user-images.githubusercontent.com github-production-user-asset-6210df.s3.amazonaws.com gist.github.com github.githubassets.com; script-src github.githubassets.com sha256-6nkh0w49y4npXaU0CPIq0z+XDtPnpaDFECgj6Y9vmx4= ; style-src unsafe-inline github.githubassets.com; upgrade-insecure-requests; worker-src github.githubassets.com github.com/assets-cdn/worker/ github.com/assets/ gist.github.com/assets-cdn/worker/
referrer-policy no-referrer-when-downgrade
server-timing pull_request_layout-fragment;desc= pull_request_layout fragment ;dur=558.587978,conversation_content-fragment;desc= conversation_content fragment ;dur=1058.552627,conversation_sidebar-fragment;desc= conversation_sidebar fragment ;dur=1237.213794,nginx;desc= NGINX ;dur=0.998701,glb;desc= GLB ;dur=67.885767
strict-transport-security max-age=31536000; includeSubdomains; preload
vary X-PJAX, X-PJAX-Container, Turbo-Visit, Turbo-Frame, X-Requested-With, X-GitHub-Client-Version, Sec-Fetch-Site,Accept-Encoding, Accept, X-Requested-With
x-content-type-options nosniff
x-frame-options deny
x-voltron-version 0d5e604
x-xss-protection 0
server github.com
content-encoding gzip
accept-ranges bytes
set-cookie _gh_sess=ay7uEI8f0NJYC5M5ikhVj22I2SIjWWuuMObbLq62%2Bk3eaTe67v1VHfp4WpVse46xTkm3ceFvy6Sot2%2BqXjJVH57vbhi5I66X120WXLXSxR2isXrHCCbCHkGwe6w48Kg4ChWD2Oy5lsmRkbe57XPNEPHzDPhMqYQXq%2BofIfGVA8KUjGpGs305SaJlBpt1pQ7OuGZfrMjLOd9QxrmxHotBz2Hkq8afARVYpylSeROldRvO4T0O2qgQVkfCRxrQRFk0%2BGtJNeBPiqB5i1L7B45hwg%3D%3D--7%2B3fMKt1KrDeG%2Bpm--587%2FCGEZaB5B%2FDVngYEiDQ%3D%3D; path=/; HttpOnly; secure; SameSite=Lax
set-cookie _octo=GH1.1.840731605.1794936697; expires=Wed, 17 Nov 2027 17:31:37 GMT; domain=.github.com; path=/; secure; SameSite=Lax
set-cookie logged_in=no; expires=Wed, 17 Nov 2027 17:31:37 GMT; domain=.github.com; path=/; HttpOnly; secure; SameSite=Lax
x-github-request-id B542:1F23AD:16540C8:1E45941:6AFC8F79
x-github-edge-region fra

Meta Tags

title="More Structured Errors? by elsiehupp · Pull Request #65 · JoshData/python-email-validator · GitHub"
charset="utf-8"
name="react-profiling" content="0" data-turbo-transient="true"
name="react-import-map" content="react,react-dom,react-dom/client,react-dom/profiling,react-is,react/compiler-runtime,react/jsx-dev-runtime,react/jsx-runtime,scheduler@b8488ee2c322" data-turbo-track="reload"
name="route-pattern" content="/_view_fragments/voltron/pull_requests/show/:user_id/:repository/:id/pull_request_layout(.:format)" data-turbo-transient
name="route-controller" content="voltron_pull_requests_fragments" data-turbo-transient
name="route-action" content="pull_request_layout" data-turbo-transient
name="fetch-nonce" content="v2:6431b8be-3d3f-2355-1742-679c8d7c471b"
name="current-catalog-service-hash" content="ae870bc5e265a340912cde392f23dad3671a0a881730ffdadd82f2f57d81641b"
name="request-id" content="B542:1F23AD:16540C8:1E45941:6AFC8F79" data-pjax-transient="true"
name="html-safe-nonce" content="af50e38e76186ddefa7402c292632cfc30e874eac913168ef5e978be067cf769" data-pjax-transient="true"
name="visitor-payload" content="eyJyZWZlcnJlciI6IiIsInJlcXVlc3RfaWQiOiJCNTQyOjFGMjNBRDoxNjU0MEM4OjFFNDU5NDE6NkFGQzhGNzkiLCJ2aXNpdG9yX2lkIjoiMzYxMDkxNDc0OTk4MzUyNjc3NyIsInJlZ2lvbl9lZGdlIjoiZnJhIiwicmVnaW9uX3JlbmRlciI6ImZyYSJ9" data-pjax-transient="true"
name="visitor-hmac" content="32ea6d94f6affe2cb031726b43cf49ed7505b063221107702800efc746fc3b79" data-pjax-transient="true"
name="hovercard-subject-tag" content="pull_request:728217682" data-turbo-transient
name="github-keyboard-shortcuts" content="repository,pull-request-list,pull-request-conversation,pull-request-files-changed,copilot" data-turbo-transient="true"
name="selected-link" value="repo_pulls" data-turbo-transient
name="google-site-verification" content="Apib7-x98H0j5cPqHWwSMm6dNU4GmODRoqxLiDzdx9I"
name="octolytics-url" content="htt????/collector.github.com/github/collect"
name="analytics-location" content="/<user-name>/<repo-name>/voltron/pull_requests_fragments/pull_request_layout" data-turbo-transient="true"
name="user-login" content=""
name="viewport" content="width=device-width"
name="description" content="A robust email syntax and deliverability validation library for Python. - More Structured Errors? by elsiehupp · Pull Request #65 · JoshData/python-email-validator"
property="fb:app_id" content="1401488693436528"
name="apple-itunes-app" content="app-id=1477376905, app-argument=htt????/github.com/_view_fragments/voltron/pull_requests/show/JoshData/python-email-validator/65/pull_request_layout"
name="twitter:image" content="htt????/opengraph.githubassets.com/c7dba1b89bfe7a0abce831f38d25edc385db5f3c1869552bd810c7285e5b7814/JoshData/python-email-validator/pull/65"
name="twitter:site" content="@github"
name="twitter:card" content="summary_large_image"
name="twitter:title" content="More Structured Errors? by elsiehupp · Pull Request #65 · JoshData/python-email-validator"
name="twitter:description" content="Problem Scope I am contributing to a project that uses python-email-validator, and a difficulty I&amp;#39;m running into is triggering custom (and possibly localized) error messages in my own (down..."
property="og:image" content="htt????/opengraph.githubassets.com/c7dba1b89bfe7a0abce831f38d25edc385db5f3c1869552bd810c7285e5b7814/JoshData/python-email-validator/pull/65"
property="og:image:alt" content="Problem Scope I am contributing to a project that uses python-email-validator, and a difficulty I&#39;m running into is triggering custom (and possibly localized) error messages in my own (downstre..."
property="og:image:width" content="1200"
property="og:image:height" content="600"
property="og:site_name" content="GitHub"
property="og:type" content="object"
property="og:title" content="More Structured Errors? by elsiehupp · Pull Request #65 · JoshData/python-email-validator"
property="og:url" content="htt????/github.com/JoshData/python-email-validator/pull/65"
property="og:description" content="Problem Scope I am contributing to a project that uses python-email-validator, and a difficulty I&#39;m running into is triggering custom (and possibly localized) error messages in my own (downstre..."
property="og:author:username" content="elsiehupp"
name="hostname" content="github.com"
name="expected-hostname" content="github.com"
http-equiv="x-pjax-version" content="3f7b67edc4d92742aa4792abf86a069f44bc24bfb20e362508ee96d855420388" data-turbo-track="reload"
http-equiv="x-pjax-csp-version" content="e6126c94b16ad4884de2cee8c82148dd37157240b73a71b763bf7f4a55426c2d" data-turbo-track="reload"
http-equiv="x-pjax-css-version" content="da37a124316120c46a7ac5f1f3faf1b2eb992aa46a47bf3bb59d2c4f87142b79" data-turbo-track="reload"
http-equiv="x-pjax-js-version" content="e3084aead77cbcb4f4904fba53851fa1a0546b0dec3619bd250815e72588dc6d" data-turbo-track="reload"
name="turbo-cache-control" content="no-preview" data-turbo-transient=""
name="turbo-cache-control" content="no-cache" data-turbo-transient
data-hydrostats="publish"
name="go-import" content="github.com/JoshData/python-email-validator git htt????/github.com/JoshData/python-email-validator.git"
name="octolytics-dimension-user_id" content="445875"
name="octolytics-dimension-user_login" content="JoshData"
name="octolytics-dimension-repository_id" content="34234240"
name="octolytics-dimension-repository_nwo" content="JoshData/python-email-validator"
name="octolytics-dimension-repository_public" content="true"
name="octolytics-dimension-repository_is_fork" content="false"
name="octolytics-dimension-repository_network_root_id" content="34234240"
name="octolytics-dimension-repository_network_root_nwo" content="JoshData/python-email-validator"
name="robots" content="noindex, nofollow"
name="turbo-body-classes" content="logged-out env-production page-responsive"
name="disable-turbo" content="false"
name="browser-stats-url" content="htt????/api.github.com/_private/browser/stats"
name="browser-errors-url" content="htt????/api.github.com/_private/browser/errors"
name="release" content="5410e4bebd3e45b138c853ecef3992279d86d5af" data-turbo-track="reload"
name="ui-target" content="full"
name="theme-color" content="#1e2327"
name="color-scheme" content="light dark"
name="react-app-name" content="pull-requests"

Load Info

page size81586
load time (s)1.514804
redirect count1
speed download53887
server IP 140.82.121.3
* all occurrences of the string "http://" have been changed to "htt???/"