Change by mike bayer :
--
nosy: +zzzeek
___
Python tracker
<https://bugs.python.org/issue47174>
___
___
Python-bugs-list mailing list
Unsubscribe:
mike bayer added the comment:
great news!
Based on how many random factors were needed to reproduce as well as that it
seemed to be gc related and appeared very suddenly, I had an intuition this was
on the cpython side, thanks so much for doing this Pablo
mike bayer added the comment:
yes, if I have time I will begin to undertake that, wanted to put it up here in
case anyone has git bisect on speed dial for cpython.
--
___
Python tracker
<https://bugs.python.org/issue44
mike bayer added the comment:
if the issue is in greenlet this can be bounced back to
https://github.com/python-greenlet/greenlet/issues/242
--
___
Python tracker
<https://bugs.python.org/issue44
New submission from mike bayer :
segmentation fault related to object deallocation and traceback objects, is
extremely difficult to reproduce and definitely appeared as of 3.10.0b2, does
not occur in 3.10.0b1. linux and osx platforms are affected.
The issue requires "greenlet==
mike bayer added the comment:
>
I don't really know why it would be a "security vulnerability", but presumably
a library could either convert their datetimes to UTC as soon as they get them
from the user if they want to use them as UTC in the future, or they could
simply ref
New submission from mike bayer :
So I'm pretty sure this is "not a bug" but it's a bit of a problem and I have a
user suggesting the "security vulnerability" bell on this one, and to be honest
I don't even know what any library would do to "prevent" this.
Ba
mike bayer added the comment:
I think this issue just discusses the naming of an attribute called
".autocommit". for the discussion for SQLite's unusual starting of
transactions, that's all in two other issues:
https://bugs.python.org/issue9924
https://bugs.python.org/issue1
mike bayer added the comment:
> Under your proposal, the first line would be changed to say
> "autocommit=True", even though not all the code below is in autocommit mode
> (according to the SQLite engine's definition). What's more, I could insert
> this line of cod
Change by mike bayer :
--
nosy: +zzzeek
___
Python tracker
<https://bugs.python.org/issue16535>
___
___
Python-bugs-list mailing list
Unsubscribe:
New submission from mike bayer :
This is likely related or a dupe of https://bugs.python.org/issue29270, but the
error message is different. I'm posting this to confirm it's the same issue,
or not, and to at least provide a google result for people who also see this
error as 29270 seems
mike bayer added the comment:
I tested "cancellation", shutting down the DB connection mid query. Because
the greenlet is only in the middle and not at the endpoints, it propagates the
exception and there does not seem to be anything different except for the
greenlet sequence in
mike bayer added the comment:
as far as cancellation, I gather you're referring to what in gevent / greenlet
is the GreenletExit exception. Sure, that thing is a PITA. Hence we're all
working to provide asyncio frontends and networking backends so that the
effects of cancellation I
mike bayer added the comment:
slight correction: it is of course possible to use gevent with a database
driver without monkeypatching, as I wrote my own gevent benchmarks using
psycogreen. I think what I'm getting at is that it's a good thing if async
DBAPIs could target asyncio explicitly
mike bayer added the comment:
> Oh, I thought the primary problem for SQLAlchemy supporting async is that the
> ORM needs to do IO from inside __getattr__ methods. So I assumed that the
> reason you were so excited about greenlets was that it would let you use
> await_() from
mike bayer added the comment:
> With greenlets OTOH, it becomes possible for another task to observe
> someobj.a == 1 without someobj.b == 2, in case someobj.__setattr__ internally
> invoked an await_().
let me try this one more time.Basically if someone wrote this:
async def
mike bayer added the comment:
> With greenlets OTOH, it becomes possible for another task to observe
> someobj.a == 1 without someobj.b == 2, in case someobj.__setattr__ internally
> invoked an await_(). Any operation can potentially invoke a context switch.
> So debugging gr
mike bayer added the comment:
yes so if you have async/await all internal, are you saying you can make that
work for synchronous code *without* running the event loop? that is, some kind
of container that just does the right thing? my concern with that would still
be performance.When
mike bayer added the comment:
> This recipe was one of the reasons why I added `loop.set_task_factory`
> method to the spec, so that it's possible to implement this in an *existing*
> event loop like uvloop. But ultimately asyncio is flexible enough to let
> users use their ow
mike bayer added the comment:
hey there,
I seem to have two cents to offer so here it is.An obscure issue in the
Python bug tracker is probably not the right place for this so consider this as
an early draft of something that maybe I'll talk about more elsewhere.
> This basica
mike bayer added the comment:
silly me thinking python devs had better access to SQLite devs :)
--
___
Python tracker
<https://bugs.python.org/issue38
mike bayer added the comment:
Hi where did you report it?I don't see it on the mailing list or in their
fossil tracker.
--
___
Python tracker
<https://bugs.python.org/issue38
New submission from mike bayer :
When using unicode characters inside of JSON strings, values retrieved via the
JSON_EXTRACT SQLite function fail to be decoded by the sqlite3 driver if they
include four-byte unicode characters.
Version information for my build, which is Fedora 30:
Python
mike bayer added the comment:
thanks for creating this issue Nick!
--
nosy: +zzzeek
___
Python tracker
<https://bugs.python.org/issue37010>
___
___
Python-bug
mike bayer added the comment:
Just did some benchmarks, and while Signature has apparently had a big speedup
in Python 3.6, it is still much less performant than either the Python 2.7 or
Python 3.3 implementations, anywhere from 6-18 times slower approximately
depending on the function
mike bayer added the comment:
> We are talking again and again that we have a lot of old things in the
> standard library but it seems that removing them is also a problem.
I agree that the reason we have these deprecation warnings is so that we do get
notified and we do fix them. I
mike bayer added the comment:
> A deprecating warning doesn't hurt: you are still able to run your code.
this is very much untrue in modern testing environments, as it is common that
test suites fail on deprecation warnings, especially in libraries, to ensure
downstream compatibility.
mike bayer added the comment:
if a function continues to work correctly throughout the span of a Python X
version, why does it need to be removed? I have a foggy memory but I don't
seem to recall functions that were technically redundant being aggressively
deprecated in the 2.x series
Change by mike bayer :
--
nosy: +zzzeek
___
Python tracker
<https://bugs.python.org/issue36751>
___
___
Python-bugs-list mailing list
Unsubscribe:
Change by mike bayer :
--
nosy: +zzzeek
___
Python tracker
<https://bugs.python.org/issue35398>
___
___
Python-bugs-list mailing list
Unsubscribe:
mike bayer <mike...@zzzcomputing.com> added the comment:
for those watching this would be the findall() case which is consistent between
pythons:
import re
for reg in [
'VARCHAR(30) COLLATE "en_US"',
'VARCHAR(30)'
]:
print(re.findall(r'(?: COLLATE.*)?$', reg
mike bayer <mike...@zzzcomputing.com> added the comment:
for now the quickest solution is to add "count=1" so that it only replaces once.
--
___
Python tracker <rep...@bugs.python.org>
<https://b
mike bayer <mike...@zzzcomputing.com> added the comment:
also, removing the "?" is not an option for me. I need the brackets to be
placed prior to the "COLLATE" subsection, but unconditionally even if the
"COLLATE" section is not present. Looking at
mike bayer <mike...@zzzcomputing.com> added the comment:
can you point me to the documentation?
--
___
Python tracker <rep...@bugs.python.org>
<https://bugs.python
mike bayer <mike...@zzzcomputing.com> added the comment:
correction, that's fedora 26, not 27
--
___
Python tracker <rep...@bugs.python.org>
<https://bugs.python
New submission from mike bayer <mike...@zzzcomputing.com>:
demo:
import re
inner = 'VARCHAR(30) COLLATE "en_US"'
result = re.sub(
r'((?: COLLATE.*)?)$',
r'FOO\1',
inner
)
print(inner)
print(result)
in all Python versions prior to 3.7:
VARCHAR(30
mike bayer added the comment:
> Here is a pure Python PoC patch that allows unbounded Queue and LifoQueue to
> have reentrant put().
per http://bugs.python.org/msg275377 guido does not want an RLock here.
--
___
Python tracke
mike bayer added the comment:
yep, that's what im doing in my approach. though longer term thing, I noticed
it's very hard to find documentation on exactly when gc might run. E.g. would
it ever run if I did something innocuous, like "self.thread_id = None"
(probably not). J
mike bayer added the comment:
SQLAlchemy suffered from this issue long ago as we use a Queue for connections,
which can be collected via weakref callback and sent back to put(), which we
observed can occur via gc.For many years (like since 2007 or so) we've
packaged a complete copy
mike bayer added the comment:
i realized this is probably with my build overall. let me do some more testing
and ill reopen if i can confirm this more closely.
--
resolution: -> works for me
status: open -> closed
___
Python tracke
New submission from mike bayer:
So I really don't know *where* the issue is in this one, because I don't know
enough about the different bits.
Step 1: Save this C program to demo.c:
#include
static PyObject *
unicode_thing(PyObject *self, PyObject *value)
{
char *str;
Py_ssize_t
mike bayer added the comment:
@rian - your issue for this is http://bugs.python.org/issue9924.
The implicit BEGIN in all cases will probably never be the default but we do
need an option for this to be the case, in order to support SERIALIZABLE
isolation
mike bayer added the comment:
@Rian - implicit transactions are part of the DBAPI spec. Looking at the
original description, the purpose of this bug is to not *end* the transaction
when DDL is received. So there's no solution for "database is locked" here,
other than pysqli
mike bayer added the comment:
thanks for the merge!
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue23898
___
___
Python-bugs-list mailing list
mike bayer added the comment:
my star went through.
let's merge.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue23898
___
___
Python-bugs-list
mike bayer added the comment:
hi Yury -
I did sign it earlier today. It should have been sent off to the person that
manages that, at least that's what the email receipt said.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org
mike bayer added the comment:
It would be great if the patch could be attached to the issue as a patch
file, including some tests.
the mantra we all share. I'll take a look.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org
mike bayer added the comment:
patch w/ test
--
keywords: +patch
Added file: http://bugs.python.org/file38882/issue23898.patch
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue23898
New submission from mike bayer:
this bug appeared in Python 3.4.The inspect.classify_class_attrs compares
the identity objects of unknown type using the `==` operator unnecessarily and
also evaluates objects of unknown type assuming they return `True` for a
straight boolean evaluation
mike bayer added the comment:
prepared statements are, in proportion to the typical speed issues in Python
(see my comparison benchmark at
https://mail.python.org/pipermail/db-sig/2014-December/006147.html) a fairly
small optimization that the DBAPI already allows for in an implicit sense
Changes by mike bayer mike...@zzzcomputing.com:
--
nosy: +zzzeek
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22956
___
___
Python-bugs-list
Changes by mike bayer mike...@zzzcomputing.com:
--
nosy: +zzzeek
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue14847
___
___
Python-bugs-list
Changes by mike bayer mike...@zzzcomputing.com:
--
nosy: +zzzeek
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22457
___
___
Python-bugs-list
New submission from mike bayer:
Per DBAPI and pysqlite docs, .description must be available for any SELECT
statement regardless of whether or not rows are returned. However, this fails
for SELECT statements that aren't simple SELECTs, such as those that use CTEs
and therefore start out
mike bayer added the comment:
my users are reporting one of these issues, and while I can easily catch
IOError on Python 2, I can't catch anything on Python 3, and pointing SIGPIPE
to SIG_DFL isn't an option because this is for Alembic migrations and the
command needs to complete its work
New submission from mike bayer:
this appears like it may be related to http://bugs.python.org/issue20786, at
least in terms of inspect.getargspec() seems to be returning answers in 3.4
where it used to raise TypeError, however like in 20786 it's again returning
the wrong answer. I'm a little
mike bayer added the comment:
see also http://bugs.python.org/issue20828 as it seems like there might be a
bigger pattern here (not sure).
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue20786
mike bayer added the comment:
I've also worked around this on my end, so if my poking into today.__call__()
isn't really a good idea anyway, I'm not doing that anymore.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue20828
mike bayer added the comment:
we basically need to be able to get the argument signature for anything that
passes callable(); function, method, class, object with __call__. So this is
the logic we use:
import inspect
def get_callable_argspec(fn):
if inspect.isfunction(fn
mike bayer added the comment:
I've got something like that going on right now, but am doing it in the other
direction; when I look at __call__(), I only do anything with it if it passes
inspect.ismethod(). Since I only want plain Python __call__() functions on
plain Python objects
New submission from mike bayer:
The Python builtin property() historically does not allow inspect.getargspec to
be called on any of __get__(), __set__(), or __delete__(). As of 3.4, it seems
that this call now succeeds. However the answer it gives for __delete__()
seems to be incorrect
Changes by mike bayer mike...@zzzcomputing.com:
--
components: +Library (Lib)
type: - behavior
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue20786
mike bayer added the comment:
for context, we are currently creating wrappers around these methods in
SQLAlchemy, and in the case of property dunders, we expect that exception and
catch it. So when the exception doesn't happen, we assume the answer is
correct, but in this case it's
mike bayer added the comment:
this is actually biting me, I think, though I'm having a very hard time getting
a small Python script to duplicate it :/.
https://bitbucket.org/zzzeek/alembic/issue/175/test-suite-failure-under-python34
refers to the current problems I'm having. I am
mike bayer added the comment:
i think I found the problem. sorry for the noise.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue17482
mike bayer added the comment:
OK well, let me just note what the issue is, and I think this is pretty
backwards-incompatible, and additionally I really can't find any reasonable way
of working around it except for just deleting __wrapped__. It would be nice if
there were some recipe
mike bayer added the comment:
see also http://bugs.python.org/issue10740, which also relates to pysqlite
attempting to make guesses as to when transactions should begin and end.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org
mike bayer added the comment:
well Adam, you might also be surprised to see pysqlite not doing very well on
the *other* side of the equation either; that is, when it *begins* the
transaction. Issue http://bugs.python.org/issue9924 refers to this and like
this one, hasn't seen any activity
Changes by mike bayer mike...@zzzcomputing.com:
--
nosy: +zzzeek
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue10740
___
___
Python-bugs-list
mike bayer added the comment:
um, this seems like a regression/bug? I now have users complaining that my
apps are broken because of this change as of Python 3.3.My application is
supposed to return the help screen when no command is given. Now I get a
None error because argparse
mike bayer added the comment:
in response to ezio, I poked around the source here, since I've never been sure
if re.compile() cached its result or not. It seems to be the case in 2.7 and
3.2 also - 2.7 uses a local caching scheme and 3.2 uses functools.lru_cache,
yet we don't see as much
Changes by mike bayer mike...@zzzcomputing.com:
--
nosy: +zzzeek
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue1062277
___
___
Python-bugs-list
mike bayer mike...@zzzcomputing.com added the comment:
I think it's fair to ask the user to setup the environment correctly
before running python setup.py install
We're supporting automatic fallback to non-C install for those environments
that don't support it. We're just looking
mike bayer mike...@zzzcomputing.com added the comment:
regarding hey this is an MS bug not Python, projects which feature optional C
extensions are starting to apply workarounds for the issue on their end (I will
need to commit a specific catch for this to SQLAlchemy) - users need to install
New submission from mike bayer mike...@zzzcomputing.com:
Copying this bug from the pysqlite tracker, at
http://code.google.com/p/pysqlite/issues/detail?id=21 , as the issue has been
opened for two days with no reply. (side node - should sqlite3 bugs be reported
here or on the pysqlite tracker
mike bayer mike...@zzzcomputing.com added the comment:
My own comment here is that I'm supposing the late BEGIN behavior is to cut
down on SQLite's file locking.I think a way to maintain that convenience
for most cases, while allowing the stricter behavior that makes SERIALIZABLE
mike bayer mike...@zzzcomputing.com added the comment:
Yeah we are fine if I build the release2.7-maint branch.Also just noticed
that this bug prevents really basic things, like using urllib2 from a Pylons
application that's running in daemon mode. Pretty major, though unusual that
I
New submission from mike bayer mike...@zzzcomputing.com:
I'm not optimistic that this will be reproducible elsewhere. I get a silent
failure with 2.6 and a crash dialog with 2.7 with the following script. All
elements are necessary, although the pkg_resources import may be arbitrary
mike bayer mike...@zzzcomputing.com added the comment:
right...so I would propose the function calls in question emit a warning or
something when called in a child process. this would save lots of people many
hours of grief.
--
___
Python tracker
mike bayer mike...@zzzcomputing.com added the comment:
where is it defined that sets are not supposed to contain mutable items?
such a requirement vastly limits the usefulness of sets.
Consider that relational database rows are mutable. A result set containing
multiple rows which each have
mike bayer mike...@zzzcomputing.com added the comment:
OK, more specifically, here's the kind of situation where items in a set are
mutable:
company = Session.query(Company).first()
# company.employees is a set()
company.employees
# each employee references the parent company
for e
New submission from mike bayer mike...@zzzcomputing.com:
given the following Python 2 source file:
# -*- encoding: utf-8
print 'bien mangé'
It can be converted to Python 3 using 2's 2to3 tool:
classic$ 2to3 test.py
... omitted ...
--- test.py (original)
+++ test.py
mike bayer mike...@zzzcomputing.com added the comment:
yes, its handled:
WARNING: couldn't encode test.py's diff for your terminal
is that fix specific to 2to3 or is that just how print works in 3.2 ?
--
___
Python tracker rep...@bugs.python.org
Changes by mike bayer mike...@zzzcomputing.com:
--
nosy: +zzzeek
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue6245
___
___
Python-bugs-list
mike bayer mike...@zzzcomputing.com added the comment:
im noticing my test case seems to work fine in py 3.0.1. haven't
tested 2.6.2.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue998998
New submission from mike bayer mike...@zzzcomputing.com:
The constructor for WeakValueDictionary does not obey the contract
documented in its comments:
# We inherit the constructor without worrying about the input
# dictionary; since it uses our .update() method, we get the right
Changes by mike bayer mike...@zzzcomputing.com:
--
components: +Library (Lib)
type: - crash
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue6149
New submission from mike bayer mike...@zzzcomputing.com:
this occurs for me running on Mac OSX Leopard. The equivalent code
using processing in python 2.5 works fine, which is how I found this
bug - my code hung when upgraded to 2.6.Basically initiating a
multiprocessing.Pool inside
mike bayer [EMAIL PROTECTED] added the comment:
This bug can be reproduced very easily:
import pickle
class MyClass(object):
pass
m = MyClass()
m2 = MyClass()
s = set([m])
m.foo = set([m2])
m2.foo = s
print pickle.dumps(s)
This bug is critical
89 matches
Mail list logo