[Python-Dev] Re: Feature Request: Python Pipes: Incluye sspipe module
I prefer keeping it as a separate library on PyPI.
On Sat, Sep 14, 2019 at 12:26 AM Juan Telleria wrote:
>
> Could sspipe module be included as part of Python's Standard Library?
>
> https://sspipe.github.io/
>
> https://github.com/sspipe/sspipe
>
> https://pypi.org/project/sspipe/
>
> sspipe allows to use syntax such as:
>
> from sspipe import p, px
> import numpy as np
> import pandas as pd
>
> (
> np.linspace(0, pi, 100)
> | p({'x': px, 'y': np.sin(px)})
> | p(pd.DataFrame)
> | px[px.x > px.y].head()
> | p(print, "Example 6: pandas and numpy support:\n", px)
> )
>
> The issue in Python's Bug Tracker is:
>
> https://bugs.python.org/issue38052
>
> Any Core Python Developer willing to support this PEP?
>
> Thank you,
>
> Juan Telleria
>
> ___
> Python-Dev mailing list -- python-dev@python.org
> To unsubscribe send an email to python-dev-le...@python.org
> https://mail.python.org/mailman3/lists/python-dev.python.org/
> Message archived at
> https://mail.python.org/archives/list/python-dev@python.org/message/2MUGDTKV5CFRXZ5LKLIBW5XB7Y3QZV6A/
--
Thanks,
Andrew Svetlov
___
Python-Dev mailing list -- python-dev@python.org
To unsubscribe send an email to python-dev-le...@python.org
https://mail.python.org/mailman3/lists/python-dev.python.org/
Message archived at
https://mail.python.org/archives/list/python-dev@python.org/message/J7RM2DSE5YXPDRP5ZOCVERHXWCIILK4D/
[Python-Dev] Re: The Python 2 death march
Hi. I've joined python-dev to participate in this thread (I don't have email delivery turned on; I'll be checking back via the web). Benjamin, I am sorry that I didn't check in with you, and assumed that January 1, 2020 would be the the date of the final 2.7 point release. (My understanding was based on Guido's EOL announcement from March last year https://mail.python.org/pipermail/python-dev/2018-March/152348.html -- I should have also gotten a review from you and not just the Steering Council in https://github.com/python/steering-council/issues/14 .) I'm going to continue this discussion here so I can make sure I understand the policy decision properly, and then (if necessary) update the FAQ. Based on what I've read here and what I see in https://www.python.org/dev/peps/pep-0373/#maintenance-releases , it sounds like the timeline will go something like: * 2019-10-19: release of 2.7.17 October * October, November, and December 2019: developers continue to fix issues in 2.7 * 2020-01-01: code freeze for 2.7.18 release candidate * January and February 2020: flexibility to fix any issues introduced since the 2.7.17 release, but no other bugs or security issues, and no 3.x backports * ~2020-04-02: release candidate for 2.7.18 * 2020-04-17: final 2.7.18 release Is this right? (If so, I can submit an update to PEP 373.) This is a little more complicated than I had anticipated when communicating out about the sunsetting. But I can find a way either to concisely communicate this, or to point to a user-friendly explanation elsewhere. Thanks. -- Sumana Harihareswara Changeset Consulting https://changeset.nyc ___ Python-Dev mailing list -- python-dev@python.org To unsubscribe send an email to python-dev-le...@python.org https://mail.python.org/mailman3/lists/python-dev.python.org/ Message archived at https://mail.python.org/archives/list/python-dev@python.org/message/MXCGMTXDY7BX6JBBU36O5YFRWWBB3NQE/
[Python-Dev] Re: python3 -bb and hash collisions
On 13Sep2019 09:31, Matt Billenstein wrote:
On Fri, Sep 13, 2019 at 08:37:26AM +1000, Cameron Simpson wrote:
On 10Sep2019 10:42, Daniel Holth wrote:
[...]
> I stopped using Python 3 after learning about str(bytes) by finding it
> in
> my corrupted database. [...]
Could you outline how this happened to you?
Not the OP, but I've actually seen something like this happen in postgres, but
it's postgres doing the adaptation of bytea into a text column, not python str
afaict:
conn = psycopg2.connect(...)
with conn.cursor() as cursor:
... cursor.execute('update note set notes=%s where id=%s returning notes',
('hi there', 'NwMVUksheafn'))
... cursor.fetchall()
... cursor.execute('update note set notes=%s where id=%s returning notes',
(b'hi there', 'NwMVUksheafn'))
... cursor.fetchall()
...
[{'notes': 'hi there'}]
[{'notes': '\\x6869207468657265'}]
We were storing the response of an api request from requests and had grabbed
response.content (bytes) instead of response.text (str). I was still able to
decode the original data from this bytes representation, so not ideal, but no
data lost.
I did wish this sorta thing had raised an error instead of doing what
it did.
Aye. Somewhere there's some Python taking the b'' and accepting it for
the notes= parameter, presumably in the postgres dbapi code. That isn't
a Python language bug to my eye. It could be some careless 2->3 adaption
I guess. I suspect it isn't postgres itself (or its C library) mangling
things, it would be accepting a C string or character buffer.
Still, I can see how this can quietly leak mojibake into your database.
Thanks,
Cameron Simpson
___
Python-Dev mailing list -- python-dev@python.org
To unsubscribe send an email to python-dev-le...@python.org
https://mail.python.org/mailman3/lists/python-dev.python.org/
Message archived at
https://mail.python.org/archives/list/python-dev@python.org/message/VCPZ6EHTXQLULVVOKJWUOLBSRB6EG2XO/
[Python-Dev] Feature Request: Python Pipes: Incluye sspipe module
Could sspipe module be included as part of Python's Standard Library?
https://sspipe.github.io/
https://github.com/sspipe/sspipe
https://pypi.org/project/sspipe/
sspipe allows to use syntax such as:
from sspipe import p, px
import numpy as np
import pandas as pd
(
np.linspace(0, pi, 100)
| p({'x': px, 'y': np.sin(px)})
| p(pd.DataFrame)
| px[px.x > px.y].head()
| p(print, "Example 6: pandas and numpy support:\n", px)
)
The issue in Python's Bug Tracker is:
https://bugs.python.org/issue38052
Any Core Python Developer willing to support this PEP?
Thank you,
Juan Telleria
___
Python-Dev mailing list -- python-dev@python.org
To unsubscribe send an email to python-dev-le...@python.org
https://mail.python.org/mailman3/lists/python-dev.python.org/
Message archived at
https://mail.python.org/archives/list/python-dev@python.org/message/2MUGDTKV5CFRXZ5LKLIBW5XB7Y3QZV6A/
[Python-Dev] Summary of Python tracker Issues
ACTIVITY SUMMARY (2019-09-06 - 2019-09-13)
Python tracker at https://bugs.python.org/
To view or respond to any of the issues listed below, click on the issue.
Do NOT respond to this message.
Issues counts and deltas:
open7031 (-92)
closed 42885 (+212)
total 49916 (+120)
Open issues with patches: 2788
Issues opened (74)
==
#34805: Explicitly specify `MyClass.__subclasses__()` returns classes
https://bugs.python.org/issue34805 reopened by rhettinger
#36871: Misleading error from unittest.mock's assert_has_calls
https://bugs.python.org/issue36871 reopened by gregory.p.smith
#37879: Segfaults in C heap type subclasses
https://bugs.python.org/issue37879 reopened by vstinner
#38047: multiarch headers are added when cross compiling
https://bugs.python.org/issue38047 opened by hhb
#38050: open('file.txt') path not found
https://bugs.python.org/issue38050 opened by Sean Frazier
#38051: time.strftime handling %z/%Z badly
https://bugs.python.org/issue38051 opened by macintux
#38052: Include sspipe Module with Core Python
https://bugs.python.org/issue38052 opened by Juan Telleria2
#38055: Starting multiprocessing.Process raises FileNotFoundError unex
https://bugs.python.org/issue38055 opened by Donny Brown
#38056: Add examples for common text encoding Error Handlers
https://bugs.python.org/issue38056 opened by Ma Lin
#38057: Docs: source code don't can be translate
https://bugs.python.org/issue38057 opened by adorilson
#38061: FreeBSD: Optimize subprocess.Popen(close_fds=True) using close
https://bugs.python.org/issue38061 opened by vstinner
#38062: Clarify that atexit.unregister matches by equality, not identi
https://bugs.python.org/issue38062 opened by mark.dickinson
#38063: Modify test_socket.py to use unittest test discovery
https://bugs.python.org/issue38063 opened by vstinner
#38065: Document the datetime capsule API
https://bugs.python.org/issue38065 opened by p-ganssle
#38067: Add headers parameter on RobotFileParser
https://bugs.python.org/issue38067 opened by eamanu
#38068: clean up configure logic for gettimeofday
https://bugs.python.org/issue38068 opened by benjamin.peterson
#38070: visit_decref(): add an assertion to check that the object is n
https://bugs.python.org/issue38070 opened by vstinner
#38073: Make pwd module PEP-384 compatible
https://bugs.python.org/issue38073 opened by dino.viehland
#38075: Make random module PEP-384 compatible
https://bugs.python.org/issue38075 opened by dino.viehland
#38077: IDLE leaking ARGV into globals() namespace
https://bugs.python.org/issue38077 opened by rhettinger
#38078: IDLE: Don't run internal code in user namespace.
https://bugs.python.org/issue38078 opened by terry.reedy
#38079: _PyObject_VAR_SIZE should avoid arithmetic overflow
https://bugs.python.org/issue38079 opened by Greg Price
#38080: 2to3 urllib fixer: missing fix for urllib.getproxies
https://bugs.python.org/issue38080 opened by shiyuchong
#38081: Different behavior of os.path.realpath('nul') in 3.7 and 3.8
https://bugs.python.org/issue38081 opened by iamsav
#38085: Interrupting class creation in __init_subclass__ may lead to i
https://bugs.python.org/issue38085 opened by xitop
#38091: Import deadlock detection causes deadlock
https://bugs.python.org/issue38091 opened by Ronan.Lamy
#38093: Update MagicMock __aenter__ and __aexit__ to return AsyncMock'
https://bugs.python.org/issue38093 opened by lisroach
#38094: unneeded assignment to wb.len in PyBytes_Concat using buffer p
https://bugs.python.org/issue38094 opened by gregory.p.smith
#38095: Multi-threaded circular import fails with _DeadlockError when
https://bugs.python.org/issue38095 opened by Ronan.Lamy
#38097: cmd.Cmd: Allow other readline completion methods
https://bugs.python.org/issue38097 opened by mannjani
#38099: __dict__ attribute is incorrectly stated to be read-only
https://bugs.python.org/issue38099 opened by reed
#38100: Spelling error in unittest.mock code
https://bugs.python.org/issue38100 opened by lisroach
#38101: Update devguide triaging keywords
https://bugs.python.org/issue38101 opened by lisroach
#38106: Race in PyThread_release_lock - can lead to memory corruption
https://bugs.python.org/issue38106 opened by navytux
#38108: Everything in Mock should inherit from Base
https://bugs.python.org/issue38108 opened by lisroach
#38109: Missing constants in Lib/stat.py
https://bugs.python.org/issue38109 opened by Ronan.Lamy
#38110: Use fdwalk() within os.closerange() impl if available
https://bugs.python.org/issue38110 opened by gregory.p.smith
#38112: Compileall improvements
https://bugs.python.org/issue38112 opened by petr.viktorin
#38115: Invalid bytecode offsets in co_lnotab
https://bugs.python.org/issue38115 opened by twouters
#38116: Make select module PEP-384 compatible
https://bugs.python.org/issue38116 opened by dino.viehland
#38118: Valgrind warnings when running tokenize.py
https://bugs.python.org/issue38
[Python-Dev] (no subject)
Hi, FYI Yury Selivanov just proposed PEP 603 which is now discussed at: https://discuss.python.org/t/pep-603-adding-a-frozenmap-type-to-collections/2318 PEP-603: Adding a frozenmap type to collections https://www.python.org/dev/peps/pep-0603/ I don't have a strong preference between python-dev or discuss.python.org to discuss PEPs, but it would be nice to send at least a notice on python-dev when a discussion on a PEP is started on discuss.python.org. Previously, almost all PEPs were posted to python-dev (except maybe packaging PEPs). Note : I like this PEP, but let's discuss it there ;-) Victor ___ Python-Dev mailing list -- python-dev@python.org To unsubscribe send an email to python-dev-le...@python.org https://mail.python.org/mailman3/lists/python-dev.python.org/ Message archived at https://mail.python.org/archives/list/python-dev@python.org/message/TTQB4EUD4CYJSO7G6GHOS5AUA2J6PJOP/
[Python-Dev] Buildbot failures
Hi, Many buildbot workers failed in the last 48 hours, it's likely related to higher activity caused by the core dev sprint currently running at London. Here are failures in random order. Can someone please have a look? I suggest to add comments to issues for collaboration. test__xxsubinterpreters: random failures on AMD64 FreeBSD CURRENT Shared 3.x https://bugs.python.org/issue38154 ERROR: test_extra_groups (test.test_subprocess.POSIXProcessTestCase) ERROR: test_group (test.test_subprocess.POSIXProcessTestCase) (group='nogroup') ERROR: test_user (test.test_subprocess.POSIXProcessTestCase) (user=65534) ERROR: test_user (test.test_subprocess.POSIXProcessTestCase) (user='nobody') https://bugs.python.org/issue36046#msg352265 AST change introduced tons of reference leaks https://bugs.python.org/issue38152 test_capi leaked [2, 2, 2] references, sum=6 https://bugs.python.org/issue38150 Victor ___ Python-Dev mailing list -- python-dev@python.org To unsubscribe send an email to python-dev-le...@python.org https://mail.python.org/mailman3/lists/python-dev.python.org/ Message archived at https://mail.python.org/archives/list/python-dev@python.org/message/KX2OANLIFFO4OF5NCPQCNAOFWTNH7FCF/
[Python-Dev] Re: python3 -bb and hash collisions
On Fri, Sep 13, 2019 at 08:37:26AM +1000, Cameron Simpson wrote:
> On 10Sep2019 10:42, Daniel Holth wrote:
> [...]
> > I stopped using Python 3 after learning about str(bytes) by finding it
> > in
> > my corrupted database. [...]
>
> Could you outline how this happened to you?
Not the OP, but I've actually seen something like this happen in postgres, but
it's postgres doing the adaptation of bytea into a text column, not python str
afaict:
>>> conn = psycopg2.connect(...)
>>>
>>> with conn.cursor() as cursor:
... cursor.execute('update note set notes=%s where id=%s returning notes',
('hi there', 'NwMVUksheafn'))
... cursor.fetchall()
... cursor.execute('update note set notes=%s where id=%s returning notes',
(b'hi there', 'NwMVUksheafn'))
... cursor.fetchall()
...
[{'notes': 'hi there'}]
[{'notes': '\\x6869207468657265'}]
We were storing the response of an api request from requests and had grabbed
response.content (bytes) instead of response.text (str). I was still able to
decode the original data from this bytes representation, so not ideal, but no
data lost.
I did wish this sorta thing had raised an error instead of doing what it did.
m
--
Matt Billenstein
m...@vazor.com
http://www.vazor.com/
___
Python-Dev mailing list -- python-dev@python.org
To unsubscribe send an email to python-dev-le...@python.org
https://mail.python.org/mailman3/lists/python-dev.python.org/
Message archived at
https://mail.python.org/archives/list/python-dev@python.org/message/CXFLFI3I3J4OQBAYLHRZSFFDU46Y4EGW/
